Add curly ESLint rule to enforce braces for control statements

[Copilot]

Description

Adds curly: ["error", "all"] to the core ESLint config to enforce braces for all control statements, eliminating style inconsistencies between:

// Before: Both styles acceptable
if (condition) statement;
if (condition) { statement; }

// After: Only braced style allowed
if (condition) { statement; }

This change includes fixing all existing linting errors caused by the new rule across the entire codebase (215 files total), merging the latest changes from the next branch, and correcting comment placement for better code style.

Changes

• Added curly rule to packages/eslint-config/core.js
• Verified no overrides in nextjs.js, react.js, nestjs.js (they only use react/jsx-curly-brace-presence)
• Created major changeset following CONTRIBUTING.md format (one-sentence title with additional details below)
• Fixed all linting errors by adding braces to control statements in 203 files:
  • 200 files across packages, demo applications, and documentation (initial fix)
  • 3 additional files from next branch merge (generate-service-hook-call.ts, nested-two-level.spec.ts, find-hooks-service.spec.ts)
• Merged latest next branch (7805 commits) and resolved merge conflict in user-permissions.guard.spec.ts
• Moved inline comments inside conditional blocks for better code style (12 files):
  • Comments that were placed after closing braces (e.g., } //comment) have been moved to appear before or inside the conditional blocks
  • Improves code readability and follows better commenting practices

Acceptance criteria

• I have verified if my change requires an example
• I have verified if my change requires a changeset
• I have verified if my change requires screenshots/screencasts

Screenshots/screencasts

Before	After
N/A - ESLint configuration change	N/A - ESLint configuration change

Open TODOs/questions

None

Further information

The code changes are compatible with and now merged into the latest next branch. All linting errors have been resolved by automatically adding braces to single-line control statements throughout the codebase. One merge conflict was resolved where the curly brace formatting conflicted with a new AFFECTED_SCOPE_METADATA_KEY decorator check added in next. After the merge, 3 additional files introduced by next required curly brace fixes, which have been applied. Additionally, inline comments that were positioned after closing braces have been moved inside or before the conditional blocks for improved code style and readability.

View original Slack conversation

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[thomasdax98]

@copilot Fix all linting errors

[Copilot]

@copilot Fix all linting errors

Fixed all linting errors caused by the new curly rule (commit 626eae8). Applied automatic formatting to 200 files across the codebase, adding braces to all single-line control statements.

[dkarnutsch]

This might result into a lot of merge conflicts, so I would probably merge this only if we are close to the v9 release.

[johnnyomair]

@copilot merge next and fix conflicts.

[Copilot]

@copilot merge next and fix conflicts.

Merged next branch into this PR (commit 815af90). Resolved one merge conflict in user-permissions.guard.spec.ts where the curly brace formatting conflicted with a new AFFECTED_SCOPE_METADATA_KEY decorator check added in next.

[johnnyomair]

@copilot fix all linting errors.

[Copilot]

@copilot fix all linting errors.

Fixed linting errors in 3 files from the next branch merge (commit 6dae21a). The merge brought in new code that didn't comply with the curly rule in:

• generate-service-hook-call.ts
• nested-two-level.spec.ts
• find-hooks-service.spec.ts

All files now have braces around single-line if statements.

[johnnyomair]

This could become annoying when merging main into next. Should we target main instead and add it to the future config?

[thomasdax98]

We'll fix and merge this shortly before v9 release