Skip to content

chore: enforce curly braces and remove deprecated eslint-env comments#1521

Merged
solaris007 merged 3 commits intomainfrom
fix/lint-curly-braces
Apr 8, 2026
Merged

chore: enforce curly braces and remove deprecated eslint-env comments#1521
solaris007 merged 3 commits intomainfrom
fix/lint-curly-braces

Conversation

@solaris007
Copy link
Copy Markdown
Member

Summary

  • Enforce curly rule introduced by @adobe/eslint-config-helix 3.0.24 - expand all single-line if/while/for bodies to multi-line with braces
  • Remove all redundant /* eslint-env mocha */ comments from 242 test files (globals already configured by the helix eslint test preset; these comments will become errors in ESLint v10)
  • Fix misplaced eslint-disable-next-line no-undef comments in html-analyzer/src/utils.js that broke after curly expansion
  • Bump @adobe/eslint-config-helix 3.0.23 -> 3.0.24 and @adobe/fetch 4.2.3 -> 4.3.0 (from renovate PR fix(deps): update adobe fixes #1503)

Test plan

  • npm run lint passes (only pre-existing no-undef in html-analyzer now fixed)
  • npm test passes across all 22 packages
  • CI passes on this branch

renovate bot and others added 2 commits April 8, 2026 09:51
eslint-config-helix 3.0.24 enables the curly rule (restrict curl to all).
Expand all single-line if/while/for bodies to multi-line with braces.
Remove redundant /* eslint-env mocha */ comments (globals already
configured by the helix eslint test preset; comments will error in
ESLint v10).
@solaris007 solaris007 changed the title fix: enforce curly braces and remove deprecated eslint-env comments chore: enforce curly braces and remove deprecated eslint-env comments Apr 8, 2026
@solaris007 solaris007 self-assigned this Apr 8, 2026
Multi-line curly brace expansion exposed pre-existing untested
defensive branches (null guards, hint logging). Add c8 ignore
comments to maintain 100% line coverage threshold.
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 8, 2026

This PR will trigger a patch release when merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant