Aaron Pettengill
Aaron Pettengill
Should be fixed in 6.3. Please feel free to re-open if it's still broken.
Hi! The current behavior is intentional, but this is definitely somewhere we can make improvements. Definitely open to ideas and discussion here! `serverValidationErrors` and `validationError` are primarily geared towards progressive-enhancement...
> And yeah I mentioned serverValidationErrors because it was the only thing I found that could in any way let me include server errors when not using Remix. Is there...
I get the feeling we're talking past each other a bit. 🫤 > What I'm proposing is kind of a compromise where we admit that RVF does accept the fact...
> Does that mean you’re ok with the way RVF behaves for the video example I uploaded in my previous comment? Those errors would use this hypothetical new API, so...
That's definitely an option. Any given form likely only needs one or two custom server errors so the burden there is small. It's certainly less work than managing your own...
That might be okay. The only thing I might worry about there would be API creep. A rough idea of the server-side api would need to cover at least this....
Closing this and one other issue in favor of #468
One reason the input and output types are different is because validation libraries like zod can encode transformations. So the data in the form itself isn't coupled to the output...
Since this isn't something we're able to do, I'm going to go ahead and close the issue. ^.^