Is there an existing issue for this?
Describe the bug
Basically reopening #18310.
Can I get more details why #18310 (comment) is an accepted answer? A more complex component can have N templates with different RenderFragment<TContext> definitions and TContext classes - does this mean that the component should have N generic arguments? This seems impractical as a non-generic component can have various RenderFragment<T> without problems.
Having a real workaround (instead of adding more and more generics) will be appreciated as we need to support versions prior to .NET 7.0 where this might have been fixed #18757
Another alternative seems to have dotnet/razor-compiler#34 ported to .NET 3.x (which is supported until Dec 2022) and .NET 6.0.
Expected Behavior
No response
Steps To Reproduce
No response
Exceptions (if any)
No response
.NET Version
No response
Anything else?
No response
Is there an existing issue for this?
Describe the bug
Basically reopening #18310.
Can I get more details why #18310 (comment) is an accepted answer? A more complex component can have N templates with different
RenderFragment<TContext>definitions andTContextclasses - does this mean that the component should have N generic arguments? This seems impractical as a non-generic component can have variousRenderFragment<T>without problems.Having a real workaround (instead of adding more and more generics) will be appreciated as we need to support versions prior to .NET 7.0 where this might have been fixed #18757
Another alternative seems to have dotnet/razor-compiler#34 ported to .NET 3.x (which is supported until Dec 2022) and .NET 6.0.
Expected Behavior
No response
Steps To Reproduce
No response
Exceptions (if any)
No response
.NET Version
No response
Anything else?
No response