Aaron Pettengill

Could you test this again with v5? I updated when we capture the form data to avoid weird race conditions caused by the async submit. So this might be fixed...

RVF v6 has been released 🎉 This should now longer be an issue in v6. If it's still a problem in that version, please feel free to open a new...

Hi! This feature is implemented in the upcoming RVF v6, so I'm going to close this PR now. Thank you again for the time you put into it!

The fact that this hook mirrors useState's api probably contributes to the confusion here. With `useState` it's safe to leave the setter of of the deps array, but here it...

RVF v6 has been released 🎉 This should no longer be an issue in v6. If it's still a problem in that version, please feel free to open a new...

RVF v6 has been released 🎉 This issue no longer exists in v6. If it's still a problem in that version, please feel free to open a new issue. You...

Looks like this might be an upstream issue in zod: https://github.com/colinhacks/zod/issues/2677

This seems reasonable. I think just having a `useFormChange` hook is probably enough for a first pass. My thinking is we would listen to any regular change event or change...

RVF v6 has been released 🎉 This should be possible now using the [subscribe api](https://www.rvf-js.io/reference/form-api#subscribe). You can find the documentation [here](https://rvf-js.io) and the migration guide [here](https://rvf-js.io/migration).

Thank you for the thorough reproduction! Definitely a weird bug. Interestingly, if you use `safeParseAsync` instead, that fixes it ([code](https://stackblitz.com/edit/vitest-dev-vitest-bjksya?file=test%2Fbasic.test.ts))? Hopefully that's a reasonable workaround for now as I'm not...