Overview - Form

form

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
36
0e933ce1 squelch react warning
by Shane Keulen
Succeeded
141
23d6b426
by pull[bot]
Succeeded
2202
3baa46b9 chore(deps): update tanstack/config digest to 10ece5e
by renovate[bot]
Succeeded
260
ece3cf48 Do not set defaultValue if model already contains value
by Tanner Lin...
Succeeded
179
c9a7cb14 Fixed issue with `setError/setWarning/setSucces`
by Alex Maroz
Succeeded
main
5d112814 ci: Version Packages (#2242) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
by github-act...
Succeeded
2242
07b70478 ci: Version Packages
by github-act...
Succeeded
main
b9c45393 ci: apply automated fixes and generate docs
by autofix-ci...
Succeeded
main
d756476b fix(react-form): use fresh FieldApi in current render on name change (#2240) * fix(react-form): use fresh FieldApi in current render on name change When a field's `name` changes (e.g. a non-last item is removed from a stably-keyed array), `useField` created a new FieldApi via `setFieldApi` during render but continued the current render pass with the stale instance. React discards that pass, but the render prop still runs to completion once with the stale FieldApi, whose store derives `undefined` for the path that no longer exists at the old index. This briefly surfaces `state.value === undefined` for surviving array items, crashing render code that treats the value strictly. Adjust state during render but also use the freshly created FieldApi for the remainder of this render, so the field reads state at its current `name`. Keeps the setState-based identity (React Compiler safe) while restoring the pre-1.27.0 behavior. Closes #2238 * chore: add changeset --------- Co-authored-by: Corbin Crutchley <git@crutchcorn.dev>
by Mark Xian
Succeeded
2240
09b74ac9 fix(react-form): use fresh FieldApi in current render on name change When a field's `name` changes (e.g. a non-last item is removed from a stably-keyed array), `useField` created a new FieldApi via `setFieldApi` during render but continued the current render pass with the stale instance. React discards that pass, but the render prop still runs to completion once with the stale FieldApi, whose store derives `undefined` for the path that no longer exists at the old index. This briefly surfaces `state.value === undefined` for surviving array items, crashing render code that treats the value strictly. Adjust state during render but also use the freshly created FieldApi for the remainder of this render, so the field reads state at its current `name`. Keeps the setState-based identity (React Compiler safe) while restoring the pre-1.27.0 behavior. Closes #2238
by MarkXian
Succeeded
main
a101fadd fix(react-form-start): align createServerValidate info param with Nex… (#2241) fix(react-form-start): align createServerValidate info param with Next.js Use FormDataInfo instead of Parameters<typeof decode>[1] so booleans, dates, and other decode options type-check correctly. Fixes #2239 Co-authored-by: Cursor <cursoragent@cursor.com>
by Hemraj bhatia
Succeeded
2240
09b74ac9 fix(react-form): use fresh FieldApi in current render on name change When a field's `name` changes (e.g. a non-last item is removed from a stably-keyed array), `useField` created a new FieldApi via `setFieldApi` during render but continued the current render pass with the stale instance. React discards that pass, but the render prop still runs to completion once with the stale FieldApi, whose store derives `undefined` for the path that no longer exists at the old index. This briefly surfaces `state.value === undefined` for surviving array items, crashing render code that treats the value strictly. Adjust state during render but also use the freshly created FieldApi for the remainder of this render, so the field reads state at its current `name`. Keeps the setState-based identity (React Compiler safe) while restoring the pre-1.27.0 behavior. Closes #2238
by MarkXian
Succeeded
2241
700cfe2f fix(react-form-start): align createServerValidate info param with Next.js Use FormDataInfo instead of Parameters<typeof decode>[1] so booleans, dates, and other decode options type-check correctly. Fixes #2239 Co-authored-by: Cursor <cursoragent@cursor.com>
by hemraj-007
Succeeded
2202
ec37b605 chore(deps): update tanstack/config digest to e6ab763
by renovate[bot]
Succeeded
140
b3f3bccd
by pull[bot]
Failed
35
cd924d6a add docs for v1.1.0
by Shane Keulen
Succeeded
259
21a48d77 Handle falsey values for defaultValue(s)
by Tanner Lin...
Succeeded
178
95c768a8 added gifs to README
by joepuzzo
Succeeded
main
397ab974 ci: Version Packages (#2237) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
by github-act...
Succeeded
2237
d29743c0 ci: Version Packages
by github-act...