Messing around with ModelsBuilder, I have been converting some old style CurrentPage views.

While I was at it I decided to derive my views from UmbracoViewPage<MyNiceModel>

The doctype for MyNiceModel contains a grid property called Content (a bit confusingly maybe) so I tried:

@Model.GetGridHtml("content", "mygridpartial")

That gives me a 'deprecated' warning though:

I therefore went with:

@Html.GetGridHtml(Model, "content", "mygridpartial")

However, that seems less elegant given that I now have to provide the Model property as a string value (so there goes one of the benefits of strongly typed models?).

Thoughts welcome.

EDIT

To avoid confusion due to my poor choice of doctype property names and to increase educational value :) this is the problem:

My Doctype has a property that is a grid, call it MyGridProperty

There are two ways to get at it in templates (i.e. views) when using ModelsBuilder:

@inherits Umbraco.Web.Mvc.UmbracoTemplatePage<ContentModels.MyDocType>
@using ContentModels = Umbraco.Web.PublishedContentModels;
...

@Model.Content.MyGridProperty

or if you go the route that V8 will ultimately go:

@inherits Umbraco.Web.Mvc.UmbracoTemplatePage

@Model.MyGridProperty

In both cases however, MyGridProperty will return as type Newtonsoft.Json.Linq.JToken because of course, grid content is stored as JSON.

That causes a problem in the sense that none of the overloads for @Html.GetGridHtml() take arguments other than IPublishedContent or alias strings as you can see here

I can somehow understand why that it is so but then again a call like:

@Html.GetGridHtml(Model, "MyGridProperty", "MyGridPartial")

Takes away some of the advantages of strong typing (because you refer to the property in string form).

Should the Grid related extension methods not be able to handle JToken arguments directly?