MVaik
MVaik
Seems to be doable with [Linked fields.](https://tanstack.com/form/latest/docs/framework/react/guides/linked-fields) You can listen to other fields on change, for example: ```js validators={{ onChangeListenTo: ['people'], onChange: ({ value, fieldApi }) => { if (!value)...
The serverValidate method returns the old values as part of the error, which get merged back over your changed state in transform. Unsure why it is done this way but...
The form receives user input, the error result just overwrites it.
Alright I get what you meant, but the reason is the same, the error result that has empty fields gets merged over state on first keypress for some reason.
Your example is private btw.
Still reproducible in 15.3.1.
Unsure if this is even the right direction, as it's essentially flipping an established default purely for react performance. Alternative could be to make disabling it opt-in instead? Would mean...
It seems like invalid state prevents the second render because FieldApi.validate returns early, which leaves out the isValidating state changes in validateAsync.