TanStack
OSS
form
Sign in / Sign up
Open main menu
form
Overview
Runs
Analytics
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Succeeded
1971
b9dc82fe fix: preserve isValidating behavior for linked fields and add test cleanup - Set current field's isValidating when linked fields have async validators (preserves original behavior) - Add vi.useRealTimers() cleanup to test
2 months ago
by tt-a1i
t
Succeeded
1971
44f43b0a fix(form-core): set isValidating synchronously before debounce delay When async validation is scheduled with debounce, the `isValidating` flag was being set AFTER an await, causing a gap where callers would see `isValidating: false` during the debounce period. This caused form.canSubmit to be true when it should be false. The fix moves the `isValidating = true` assignment to happen synchronously, before any await, when async validators are detected. Fixes #1833
2 months ago
by tt-a1i
t
Canceled
1930
14cfd653 fix(react-form): prevent array field re-render when child property changes Array fields with `mode="array"` were incorrectly re-rendering when a property on any array element was mutated. This was a regression introduced in v1.27.0 by the React Compiler compatibility changes. The root cause was that `reactiveStateValue` subscribed to the entire `state.value`, which changes whenever any child property changes. For array mode, this subscription now only tracks the array length, ensuring re-renders only occur when items are added or removed. - Modified `reactiveStateValue` to use array length selector for array mode - Updated `state.value` getter to return actual value from `fieldApi.state.value` - Removed redundant `useStore` subscription for array mode - Added test case to verify array field doesn't re-render on child changes Fixes #1925
2 months ago
by tt-a1i
t
Canceled
1929
89c5741e fix(form-core): prevent double re-render when no async validators Fields were re-rendering twice on each keystroke because `isValidating` was being toggled (true -> false) even when there were no async validators. This fix checks if there are actual async validators before setting `isValidating` state, preventing unnecessary re-renders. Fixes #1130
2 months ago
by tt-a1i
t
Previous page
Previous
Next
Next page