Replies: 1 comment
-
Indeed, I just ran into a similar issue. I have 1 field in my form that is validating correctly, but it's non-critical. I want to warn the user but not prohibit the form submission. I can fix the cosmetics of how the validation error is displayed so it looks right, but I am uncertain how to 'ignore' the 'error' and submit the form. If someone has a suggestion for a work-around it would be most welcome. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I just came across a use case where we need to show a warning or hint if a user for example wants to name an entity he creates the same as one that already exists. He should be able to submit the form if he likes but it should at least be clear to him that a similar thing already exists.
In theory there could of course be multiple different severity levels for this which have different priorities for displaying them to the user like for example error > warning > info.
Maybe it's something that could be implemented in the future. I also found the same feature request for other validation libraries which explain this a bit better. Seems to be a great feature if the application is form heavy.
react-hook-form/react-hook-form#1761
jaredpalmer/formik#389
Beta Was this translation helpful? Give feedback.
All reactions