Currently ComponentParameterBuilder checks in the Add methods whether a parameter exists in the component under test, that matches the type passed as a cascading value. If a user wants to test a CUT that does not use the cascading value itself, but has sub components that does, they cannot use the builder.
My current thinking is that the existing Add(object) method be replaced with `AddCa
Bootstrap.NET is a strongly typed version of Bootstrap implemented in Razor Components, with a nice Bootstrap-like syntax for specifying options on components. On top of that, you get compile-time errors if you try to assign invalid options to components.
An advanced Blazor example demonstrating a Razor class library with embedded JavaScript shared between a Blazor Server and a Blazor WebAssembly project.
This is Blazor Web Assemble App which can run on Client Machine with Server side functionality. Also used Entity Framework Core, Dependency Injection, Table Relationship and more.
An extension of standard ASP.NET Core View components which allows to easily create components with added JavaScript/TypeScript functionality for ASP.NET projects.
It would be good to have a easy way to disable a MatTab by just passing a prop.