[v2] chore(examples): replace leftover template package names and page titles - #2405
dasjideepak wants to merge 1 commit into
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: TanStack/form/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (15)
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughReact example package names and page titles now identify TanStack Form and the specific example. The changeset entry for the Next.js example uses its updated package name; its version remains unchanged. ChangesReact example metadata
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~4 minutes Change: Other Merge Risk: ⚪ Minimal · up to The changes update example package names and page titles without changing the Next.js version. No stale references to the old package names were found, so no material merge risk remains. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 1 system. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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. Comment |
|
View your CI Pipeline Execution ↗ for commit deafbac
☁️ Nx Cloud last updated this comment at |
🎯 Changes
First PR for #2305. It covers the first two checklist items: leftover TanStack Template wording, and duplicate or incorrect package names.
Package names. Eight React examples didn't follow the
@tanstack/form-example-<framework>-<folder>pattern the other examples use:@tanstack/template-example-react-array@tanstack/form-example-react-array@tanstack/template-example-react-basic@tanstack/form-example-react-basic@tanstack/template-example-react-basic-splitting-form@tanstack/form-example-react-basic-splitting-form@tanstack/template-example-react-field-group@tanstack/form-example-react-field-groups@tanstack/template-example-react-nextjs@tanstack/form-example-react-nextjstanstack-start-example-basic@tanstack/form-example-react-tanstack-start@tanstack/tanstack-form-example-react-dnd-kit@tanstack/form-example-react-ui-integration-dnd-kit@tanstack/tanstack-form-example-react-shadcn-ui@tanstack/form-example-react-ui-integration-shadcnThere were no duplicate names left once these were fixed.
Template wording. Six of those examples still had
<title>TanStack Template - React Basic Example</title>. They now have a title that names the example, e.g.TanStack Form React Field Groups Example. I kept the change to the titles only; aligning the rest of theheadconfig across examples is the next PR..changeset/pre.json.react/nextjsis the only example with aversion, so it's listed ininitialVersionsunder the old name. I renamed that key to match. If you'd rather not touch the pre-release file, I can drop that line.Nothing references the old names elsewhere: the lockfile keys importers by path, and
pnpm install --frozen-lockfilepasses unchanged.✅ Checklist
pnpm test:pr, or these tests do not apply to this pull request. (Example metadata only;pnpm test:sherifandpnpm test:knippass.)🚀 Release Impact
@LeCarbonator, ready for review. Next up: the port and
headconfig, then devtools and StrictMode.Summary by CodeRabbit