Need to re-visit unmounted fields in order for the validators to update the errors
Hello!
I've encountered a pretty strange behaviour in my form setup. Here's a minimal reproducible example showcasing this issue I'm facing.
https://stackblitz.com/edit/vitejs-vite-p3tjgchh?file=src%2Fmain.tsx
This form is organised in multiple tabs, and has two submit actions; publish and draft. These two actions have different requirements (schemas).
I found that sometimes the form won't let me submit a draft even though it should because it still has some errors of the previous "publish" validation. In order to mitigate this I'm using
Long story short, in order to submit a draft I need to revisit the tabs that had errors in the previous validation cycle.
Steps to reproduce:
1- Go to tab 1 (by default the first tab shown will be the second)
2- Try to publish the -empty- article. The validation will fail (as expected).
3- Try to save a draft. Given that an empty article is a valid draft, it should call the
4- Go back to tab 2 and save a draft. Now, after the "invalid" fields have been revisited it actually submits the form, even though no fields have been touched.
In order to see if this was an issue with tanstack form or not I recreated the exact same scenario with react-hook-form, and it works much more like I'd expect.
RHF implementation: https://stackblitz.com/edit/vitejs-vite-248nogko?file=src%2Fmain.tsx
Is this a known issue?
I've encountered a pretty strange behaviour in my form setup. Here's a minimal reproducible example showcasing this issue I'm facing.
https://stackblitz.com/edit/vitejs-vite-p3tjgchh?file=src%2Fmain.tsx
This form is organised in multiple tabs, and has two submit actions; publish and draft. These two actions have different requirements (schemas).
I found that sometimes the form won't let me submit a draft even though it should because it still has some errors of the previous "publish" validation. In order to mitigate this I'm using
canSubmitWhenInvalidLong story short, in order to submit a draft I need to revisit the tabs that had errors in the previous validation cycle.
Steps to reproduce:
1- Go to tab 1 (by default the first tab shown will be the second)
2- Try to publish the -empty- article. The validation will fail (as expected).
3- Try to save a draft. Given that an empty article is a valid draft, it should call the
saveArticle4- Go back to tab 2 and save a draft. Now, after the "invalid" fields have been revisited it actually submits the form, even though no fields have been touched.
In order to see if this was an issue with tanstack form or not I recreated the exact same scenario with react-hook-form, and it works much more like I'd expect.
RHF implementation: https://stackblitz.com/edit/vitejs-vite-248nogko?file=src%2Fmain.tsx
Is this a known issue?
