You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In version 0.32.0, canSubmit became true with valid values (e.g., '5' or '6'), but in version 0.33.0, canSubmit remains false.
Expected behavior
I want validation to be executed when setFieldValue is called.
How often does this bug happen?
Every time
Platform
OS: Mac
Browser: Chrome
TanStack Form adapter
react-form
TanStack Form version
v0.33.0
TypeScript version
v5.6.3
Additional context
If I execute validateField after every setFieldValue call, the validation runs and behaves as expected. However, this was not necessary in version 0.32.0. I would like to know if this behavior is intentional or a bug.
If the form validator has field errors they're spread into the fields, but if there are no (more) errors, nothing happens.
This means that if there are existing errors they're not removed and that's our bug.
Should be fixed on validateSync and validateAsync.
Describe the bug
When using zodValidator, even if I set a valid value with setFieldValue, canSubmit does not become true
In version 0.32.0, canSubmit became true with valid values (e.g., '5' or '6'), but in version 0.33.0, canSubmit remains false.
Expected behavior
I want validation to be executed when setFieldValue is called.
How often does this bug happen?
Every time
Platform
TanStack Form adapter
react-form
TanStack Form version
v0.33.0
TypeScript version
v5.6.3
Additional context
If I execute validateField after every setFieldValue call, the validation runs and behaves as expected. However, this was not necessary in version 0.32.0. I would like to know if this behavior is intentional or a bug.
like this.
I think the behavior change might be due to the changes introduced in #925 , but I'm not certain.
The text was updated successfully, but these errors were encountered: