| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Caution Review failedThe pull request is closed. Configuration used: defaults Review profile: CHILL Plan: Pro Run ID: 9113c641-f02e-4bf7-964e-963126b1747b 📥 CommitsReviewing files that changed from the base of the PR and between 7ca1cbc and 9b21c73. 📒 Files selected for processing (1)
📝 Walkthrough WalkthroughFormApi.update now detects array-typed field values and bumps their array metadata versions when values update. A regression test confirms async-resolved array defaultValues re-render the array field, and a changeset records a patch bump for @tanstack/form-core. ChangesArray Field Async Value Resolution Fix
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Suggested reviewers
Poem🚥 Pre-merge checks | ✅ 4 | ❌ 1 ❌ Failed checks (1 warning)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches 🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. ❤️ ShareComment @coderabbitai help to get the list of available commands and usage tips. |
Sorry, something went wrong.
There was a problem hiding this comment.
This fix makes a lot of sense. Thanks for the PR and tests
Sorry, something went wrong.
|
View your CI Pipeline Execution ↗ for commit 7f33ac6
☁️ Nx Cloud last updated this comment at 2026-05-26 14:59:46 UTC |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agentsVerify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@packages/react-form/tests/useField.test.tsx`:
- Line 1546: The test fails because the <ol> element uses the wrong attribute
name `data-mtestid="list"`; update that attribute to `data-testid="list"` so the
test's calls to getByTestId('list') can find the element—search for the <ol> in
the useField.test.tsx test and replace `data-mtestid` with `data-testid` where
the list is rendered.
Fix all unresolved CodeRabbit comments on this PR:
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: ebbab2ab-e11a-4a15-b313-5202306a23bb
📥 CommitsReviewing files that changed from the base of the PR and between a771a95 and 7ca1cbc.
📒 Files selected for processing (1)
Sorry, something went wrong.
|
⚠️ Please install the Codecov Report❌ Patch coverage is 80.00000% with 1 line in your changes missing coverage. Please review.
@@ Coverage Diff @@
## main #2190 +/- ##
==========================================
+ Coverage 90.35% 91.42% +1.06%
==========================================
Files 38 59 +21
Lines 1752 2343 +591
Branches 444 585 +141
==========================================
+ Hits 1583 2142 +559
- Misses 149 180 +31
- Partials 20 21 +1 ☔ View full report in Codecov by Sentry.
|
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fixes #2178
When async defaultValues resolve and update the form, array fields rendered with mode="array" were not re-rendering. This is a regression from #2172 which changed the array field reactivity signal from Object.keys(value ?? []).length to state.meta._arrayVersion. The _arrayVersion counter is bumped on explicit mutations (push/insert/remove/swap/move) but not when defaultValues change asynchronously.
The fix: after the store update in FormApi.update(), iterate over registered fields and bump _arrayVersion for any whose current value is an array. Added a regression test.
Summary by CodeRabbit
Bug Fixes
Tests
Chores