Upgrade Biome to v2.2.0 and implement React recommended rules

[jaruesink]

Summary by CodeRabbit

• New Features

  • Inline editing for todo items with validation, save, and cancel controls.

• Style

  • Widespread import/order and whitespace cleanups across app and UI packages.

• Chores

  • Updated formatting/linting configuration and dev dependency to the latest Biome.

• Tests

  • Streamlined test imports and setup; no behavioral changes.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Adds inline edit flow in TodoItem using remix-hook-form and Zod validation. Broadly reorganizes imports across app, UI, and tests. Updates Biome config to 2.2.0 with schema and rule changes; bumps @biomejs/biome in multiple package.json files. Minor formatting in Vitest configs and setup files. No public API changes except reordered exports.

Changes

Cohort / File(s)	Summary
TodoItem inline editing apps/todo-app/app/components/todo-item.tsx	Implements inline edit form with useRemixForm, zodResolver, and editTodoSchema; adds isEditing state, submit/cancel handlers, validation, and RemixFormProvider-wrapped UI. Public props unchanged.
Add Todo + tests formatting apps/todo-app/app/components/add-todo.tsx, apps/todo-app/app/components/__tests__/add-todo.test.tsx	Reorder imports and minor formatting; no logic changes.
Todo context + tests formatting apps/todo-app/app/lib/todo-context.tsx, apps/todo-app/app/lib/__tests__/todo-context.test.tsx	Import reordering and formatting in source and tests; no behavior changes.
Routes adjustments apps/todo-app/app/routes/create-todo.tsx, apps/todo-app/app/routes/home.tsx, apps/todo-app/app/root.tsx	Import reordering; home.tsx adds/imports UI components/icons used by existing JSX; no control-flow changes.
Test setup and configs apps/todo-app/test/setup.ts, apps/todo-app/vitest.config.ts, packages/ui/src/test/setup.ts, packages/ui/vitest.config.ts, apps/todo-app/vite-env.d.ts	Formatting and import order tweaks; remove trailing commas/blank lines; no functional impact.
Biome upgrade and config biome.json	Update schema to 2.2.0; rename files.include→files.includes with explicit excludes; add assist.enabled; adjust formatter settings; switch linter to recommended with category tweaks and new a11y block; remove organizeImports and “all” flags.
Biome version bumps package.json, packages/ui/package.json, packages/utils/package.json	Bump @biomejs/biome to 2.2.0 in devDependencies.
UI components import/order packages/ui/src/components/ui/button.tsx, .../card.tsx, .../checkbox.tsx, .../input.tsx, packages/ui/src/components/ui/button.test.tsx	Reorder imports in components and a test; no logic changes.
UI public exports reorder packages/ui/src/index.ts	Reorder existing exports (Button/Card/Input lines); no added/removed symbols.
Utils tests formatting packages/utils/src/cn.test.ts, packages/utils/src/types.test.ts	Reorder vitest imports; minor formatting of stub functions; no behavioral changes.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor U as User
  participant TI as TodoItem
  participant F as useRemixForm
  participant Z as Zod (editTodoSchema)
  participant S as Todo Store

  U->>TI: Click "Edit"
  TI->>F: init form { defaultValues: { text: todo.text }, resolver: zodResolver(Z) }
  TI->>U: Render TextField + [Save ✓][Cancel ✕]

  alt Cancel
    U->>TI: Click "Cancel"
    TI->>F: reset({ text: original })
    TI->>U: Exit editing mode
  else Save
    U->>TI: Submit form
    TI->>F: validate via Z
    alt Valid and changed
      TI->>S: updateTodo(id, newText)
      TI->>U: Exit editing mode
    else Invalid or unchanged
      TI->>U: Show FormError / stay in edit
    end
  end

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• 🚀 Integrate @lambdacurry/forms library with comprehensive examples #3 — Introduces similar inline editing to TodoItem using remix-hook-form/Zod, indicating parallel or preceding work on the same feature.

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between b034ea2 and 4299449.

⛔ Files ignored due to path filters (1)

• bun.lock is excluded by !**/*.lock

📒 Files selected for processing (25)

• apps/todo-app/app/components/__tests__/add-todo.test.tsx (1 hunks)
• apps/todo-app/app/components/add-todo.tsx (1 hunks)
• apps/todo-app/app/components/todo-item.tsx (1 hunks)
• apps/todo-app/app/lib/__tests__/todo-context.test.tsx (3 hunks)
• apps/todo-app/app/lib/todo-context.tsx (1 hunks)
• apps/todo-app/app/root.tsx (1 hunks)
• apps/todo-app/app/routes/create-todo.tsx (1 hunks)
• apps/todo-app/app/routes/home.tsx (1 hunks)
• apps/todo-app/test/setup.ts (1 hunks)
• apps/todo-app/vite-env.d.ts (0 hunks)
• apps/todo-app/vitest.config.ts (1 hunks)
• biome.json (3 hunks)
• package.json (1 hunks)
• packages/ui/package.json (1 hunks)
• packages/ui/src/components/ui/button.test.tsx (1 hunks)
• packages/ui/src/components/ui/button.tsx (1 hunks)
• packages/ui/src/components/ui/card.tsx (1 hunks)
• packages/ui/src/components/ui/checkbox.tsx (1 hunks)
• packages/ui/src/components/ui/input.tsx (1 hunks)
• packages/ui/src/index.ts (1 hunks)
• packages/ui/src/test/setup.ts (0 hunks)
• packages/ui/vitest.config.ts (1 hunks)
• packages/utils/package.json (1 hunks)
• packages/utils/src/cn.test.ts (1 hunks)
• packages/utils/src/types.test.ts (2 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch codegen/sta-16-upgrade-biome-to-latest-version-starter

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.