We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Reading through https://tanstack.com/form/latest/docs/framework/react/guides/listeners#form-listeners, I tried to implement the auto-save functionality. The onChange is being triggered but the submit method doesn't trigger the action attached to the form (not calling the server).
onChange
action
https://tanstack.com/form/latest/docs/framework/react/guides/listeners#form-listeners
The action is being triggered when the form is being submitted through the auto-save with the listeners.onChange debounce.
listeners.onChange
None
No response
MacOS, Chrome
1.11.1
The text was updated successfully, but these errors were encountered:
I found out that this is triggering the onSubmit method from the useForm, which is on the client-side.
onSubmit
useForm
Sorry, something went wrong.
No branches or pull requests
Describe the bug
Reading through https://tanstack.com/form/latest/docs/framework/react/guides/listeners#form-listeners, I tried to implement the auto-save functionality. The
onChange
is being triggered but the submit method doesn't trigger theaction
attached to the form (not calling the server).Your minimal, reproducible example
https://tanstack.com/form/latest/docs/framework/react/guides/listeners#form-listeners
Steps to reproduce
Expected behavior
The action is being triggered when the form is being submitted through the auto-save with the
listeners.onChange
debounce.How often does this bug happen?
None
Screenshots or Videos
No response
Platform
MacOS, Chrome
TanStack Form adapter
None
TanStack Form version
1.11.1
TypeScript version
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: