-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] - Form validation errors not displaying via the validationErrors #4648
Comments
Couldn't reproduce the issue. Please provide a sandbox instead. |
Ok. Let me some time for it |
You can check it - sandbox I copied the package.json from my test project into a sandbox because I suspect the issue lies with the @heroui dependencies. I’ve made many attempts to reproduce the issue, deleting node_modules and the lock file, then reinstalling the dependencies. As a result, sometimes the form and input errors work correctly. Additionally, I noticed that the fewer component dependencies I include in package.json, the more often the form works correctly. Possibly, the issue is with a library used internally by heroui as one of its dependencies. |
I'm having the same issue and my code and dependencies appear to be same as @kofeinstyle. Just adding that validationBehavior="native" for client side validation consistently works, but setting validationErrors does not. As an override, I can set isInvalid and errorMessage on heroui Input components, but then I lose the client side validation. Is there a way to get the controlled values from the Form component?
|
HeroUI Version
@heroui/[email protected]
Describe the bug
I am trying to use the example from the documentation (https://www.heroui.com/docs/components/form#validation), but no errors are displayed on the input field, and the form does not respond to the presence of errors.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
Expected behavior
Highlight errors on input field
Screenshots or Videos
No response
Operating System Version
macOS
Browser
Chrome
The text was updated successfully, but these errors were encountered: