Component-library support beyond MudBlazor (Radzen, Telerik, FluentUI) #3

Came up in launch comments. Today the component-action wrappers are MudBlazor-coupled. The capability/workflow model is library-agnostic.

Open question: should the wrapper layer abstract over multiple libraries, or commit harder to MudBlazor and let other libraries plug in via custom wrappers? Tracked from Reddit launch thread.