-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
better server error handling #402
Comments
I'd suggest making a derived/proxy store for this, based on |
I see what you mean, unfortunately I don't see a way for this to work with I have the feeling it would be much easier to handle this internally like providing a way to merge server errors with superForms errors or otherwise I feel like there will be a lot of side-effects. |
Now I managed to display server errors with I created a repro to demonstrate the issue: |
Is your feature request related to a problem? Please describe.
Currently the handling of server side errors is a big pain. Our situation is that we have server errors like these:
and we want to automatically set form errors based on these server errors.
We can't do this:
because the errors vanish as soon as someone modifies an input field.
I also tested other hacky solutions like this one with a recursive
refine
that checks for errors in the error store that match with a field of the zod schema:But here we have a separate errorStore where we store all server errors after submit but like that we have race conditions because
refine
runs before the errors are set. and it generally feels really hacky.Describe the solution you'd like
It would be really nice if we had a nice way to let superforms handle these things natively or provide a way to make the manually set errors not vanish on form modifications.
Describe alternatives you've considered
validationMethod: "submit-only"
works but is turning off early validation for the whole schemaThe text was updated successfully, but these errors were encountered: