Proposed Changes

Issue #13156 reports an unexpected transition in formState.isValidating when using a resolver. During validation, isValidating briefly flips from true to false before the resolver has finished updating errors, which makes the form temporarily look valid even though validation hasn’t finished yet.

After investigating, the cause is that the current implementation updates isValidating inside an async function containing an await, which breaks React’s state batching. As a result, the isValidating: false update is emitted separately from the subsequent errors and other updates.

Relevant code:

Because the second _updateIsValidating runs after an awaited promise, React flushes it independently, creating an intermediate inconsistent state:

• isValidating === false
• errors[field] === undefined

This is exactly what the reproduction shows.

Changes

To ensure isValidating: false is batched together with the resolver result and the following state updates, the call to _updateIsValidating(name) has been moved out of _runSchema and placed immediately after the await _runSchema(...) call.

This guarantees the state transition occurs in the same flush as the resolver output, preventing the temporary invalid intermediate state.

Type of change

• Bug fix (non-breaking change which fixes an issue)

fixes: #13156

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing tests pass locally with my changes