You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe the problem.
For invalid form fields, the razor engine outputs hardcoded css class names: input-validation-error, input-validation-valid, field-validation-error, field-validation-valid, etc.
When using a ui library (bootstrap, tailwind, etc.) one needs different classes. For example, for bootstrap it's is-invalid, is-valid, invalid-feedback, valid-feedback, etc.
One can rename these in JS, but that is a hack. It also makes it very difficult to use various js libraries.
Describe the solution you'd like
Please allow us to customise those class names during startup.
Additional context
This problem goes back years. I realise that #8573 and #40935 are not going to be done in the short term.
So at least allow us to change the css class names, which will give us more flexibility for now.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
For invalid form fields, the razor engine outputs hardcoded css class names:
input-validation-error
,input-validation-valid
,field-validation-error
,field-validation-valid
, etc.When using a ui library (bootstrap, tailwind, etc.) one needs different classes. For example, for bootstrap it's
is-invalid
,is-valid
,invalid-feedback
,valid-feedback
, etc.One can rename these in JS, but that is a hack. It also makes it very difficult to use various js libraries.
Describe the solution you'd like
Please allow us to customise those class names during startup.
Additional context
This problem goes back years. I realise that #8573 and #40935 are not going to be done in the short term.
So at least allow us to change the css class names, which will give us more flexibility for now.
The text was updated successfully, but these errors were encountered: