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
Hi guys. When I updated the css class name customisation docs, I didn't take into account server-rendered pages which already contain errors.
For example: form submission fails due to validation errors, so page is rerendered, but with ASP.NET Core's css class names (input-validation-error and input-validation-valid). Those are incorrect in my case, as I'm using bootstrap (so I need is-invalid and is-valid). I assume the same problem exists for those using tailwind, etc.
I'd like to change those css class names so they match what is used by this library.
Although it's not an issue with this library, it's nonetheless related. Does anyone have a server-side customisation technique for this?
(Once I find a solution, I'll also update the docs.)
The text was updated successfully, but these errors were encountered:
That is one big LOL given that I already asked that question and you already answered it. Do you ever find that years go by and you encounter the same problem, search for the same solutions, and discover one written by you on StackOverflow or GitHub or whatever? 😆
Hi guys. When I updated the css class name customisation docs, I didn't take into account server-rendered pages which already contain errors.
For example: form submission fails due to validation errors, so page is rerendered, but with ASP.NET Core's css class names (
input-validation-error
andinput-validation-valid
). Those are incorrect in my case, as I'm using bootstrap (so I needis-invalid
andis-valid
). I assume the same problem exists for those using tailwind, etc.I'd like to change those css class names so they match what is used by this library.
Although it's not an issue with this library, it's nonetheless related. Does anyone have a server-side customisation technique for this?
(Once I find a solution, I'll also update the docs.)
The text was updated successfully, but these errors were encountered: