Gareth Leachman
Gareth Leachman
Currently the Markup needs ``` Simple Widgets @Item.Id ``` We would like to remove the need for the `` tag ``` ``` and be able to use the HeaderStyle using...
**DevNotes** Blazor team commit for error message on [Templated Components](https://github.com/dotnet/blazor/pull/1404/commits/99b6cdd0cf67d01f65b9485f430e767d963f1d20) and [test](https://github.com/dotnet/blazor/blob/99b6cdd0cf67d01f65b9485f430e767d963f1d20/src/Microsoft.AspNetCore.Blazor.Razor.Extensions/ComponentLoweringPass.cs) I suspect this is another [by design](https://github.com/dotnet/aspnetcore/issues/10836) feature Note the comment > Thanks for your feedback, @Venkat4655. We'll...
Are you wanting to not have to convert explicitly ``` @Item.Id @Item.Name @Item.Price.ToString("c") @Item.LastUpdate.ToString("d") ``` where the **Context="Item"** changes `@context` to `@item` What you want is for the `BlazorWebFormsComponents.ListView` to...
Some reading [dotnet/Blazor merge for : Adds support for 'Context' parameters](https://github.com/dotnet/blazor/pull/1470/commits)
The commit is actually against an internal `ComponentTagHelper…` but it gives a place to start. ### L276 however it all looks very internal. Without thinking about how this might actually...
BlazorWebFormComponents needs to be able to access the TagHelperDescriptorBuilder here, and apply the same behaviour as the CreateContextParameter with the `childContentName = item` ``` private void CreateContextParameter(TagHelperDescriptorBuilder builder, string childContentName)...
The test for this in Blazor : [ChildContentRazorIntegrationTest](https://github.com/dotnet/aspnetcore/blob/master/src/Components/Blazor/Build/test/ChildContentRazorIntegrationTest.cs) see : * Render_MultipleChildContent_ContextParameterOnComponent * Render_MultipleChildContent_ContextParameterOnComponent_SetsSameName  Notice how the **`Context="Item"`** attribute does not actually appear in the component's Frames.
While it would be fun to research this further, and find some point of DI that could subvert the Blazor teams deliberate enforcement of the `context` syntax. I think there...
it might be nice if the Blazor team add some specific `WebFormsSupport()`. ` services.AddWebFormsSupport();` This might do things like … - override the internal ?TagHelper? that manages / sets the...
#49 another unsupported (but we'll do it if the community shouts loud enough)