blazor-ui-kit

You decouple Radzen UI components by wrapping them with French-named Blazor wrappers like GrilleDonnees, Dialogue, and Bouton. This prevents Presenters from referencing Radzen types directly, ensuring frontend portability and consistency across multiple pages.

The best way to enforce consistent UI defaults is to centralize them inside Blazor wrappers. Imposing wrapper conventions and default values ensures all Presenters use standardized configurations, reducing direct component coupling and maintaining uniform behavior across pages.

You wire dependency injection for Blazor UI wrappers by imposing DI conventions that supply wrapper instances to Presenters. This integration ensures Presenters avoid referencing Radzen types directly while maintaining clean architectural boundaries within the hexagonal frontend.

Yes, you can name Blazor UI wrappers using French business vocabulary like GrilleDonnees, Dialogue, Bouton, and ChampTexte. This naming convention aligns the UI components with domain terminology while maintaining clean separation from Radzen types.

Yes, the Blazor UI kit approach works without direct Radzen type dependencies. By applying wrappers and dependency injection wiring, Presenters avoid referencing Radzen types entirely, which limits coupling and facilitates future component replacement.

You should not use wrapper components for Blazor UI encapsulation when your project requires rapid prototyping with minimal architectural overhead or when direct Radzen coupling does not pose a portability risk for your specific application scale.