Add extensibility point for EditContext FieldCSSClass for Blazor forms - The current options are too limited

[ericgholland]

Is your feature request related to a problem? Please describe.

The current implementation of FieldCSSClass as a baked in extension method is limited to only some combination of "modified", "valid", or "invalid". With something as important as form editing context, we need to be able to extend this with other options such as warning, busy, readonly, disabled, hidden etc... Don't limit this to a predefined set, let the developer customize as needed

Describe the solution you'd like

Simply add the ability to override the default behavior. A simple option would be to allow an action to be assigned to the editcontext. If its assigned, then allow that action to determine the cssclass for the field. A better option would be to change the current implementation into something more modular by adding adding an interface like IFieldCSSClassProvider and then allowing a custom provider to be plugged in.

Additional context

Most css frameworks already support other options - especially warning, so it would make sense to allow this extensibility point for developers.

[pranavkm]

Thanks for the issue report. We'll consider this issue during our next planning.

[danielxbauer]

I would also welcome an easy way to modify the default css class names. Currently these names ("modified", "valid", "invalid", ...) are hardcoded.

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.