Skip to content

fix: resolve format-check CI failures (biome format + import order) - #188

Open
Trosper3 wants to merge 2 commits into
ReduxAPI_GUIfrom
fix/format-check-181
Open

fix: resolve format-check CI failures (biome format + import order)#188
Trosper3 wants to merge 2 commits into
ReduxAPI_GUIfrom
fix/format-check-181

Conversation

@Trosper3

@Trosper3 Trosper3 commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Runs npm run format (biome check --write .) to fix the 58 formatting and 33 import-order violations flagged by the format-check CI job (quote style, semicolons, indentation, import ordering/merging).
  • Runs biome migrate to bring biome.json's $schema up to the installed Biome 2.5.8 (was pinned at 2.5.3).

Test plan

  • npm run format:check passes cleanly (was 117 errors, now 0)
  • npm run lint produces the same 65 problems (24 errors, 41 warnings) before and after — confirmed via stash/pop comparison, so no lint regressions
  • npm run build succeeds
  • Spot-checked diffs (Data.json, StandardSATSvgReact.js) — purely mechanical reformatting/import reordering, no logic changes

Closes #181

🤖 Generated with Claude Code

Run `npm run format` (biome check --write .) to fix 58 formatting and
33 import-order violations across ~30 files, and `biome migrate` to
bring biome.json up to the installed 2.5.8 schema. Mechanical only:
quote/semicolon/indent normalization, import reordering, and 4->2
space reindent in Data.json. No logic changes; lint results unchanged
(65 problems, pre-existing) and build succeeds.

Closes #181

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01K5wXdN2yC9f8vuAuXBVCNo

@github-advanced-security github-advanced-security AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ESLint found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.

Comment thread Tools/ProblemInstanceParser.js Fixed
@github-actions

github-actions Bot commented Aug 28, 2026

Copy link
Copy Markdown

Redux Build System — CI Report

npm · commit 92fcac3

Operation Status Summary Time
audit 1 high 0.6s
format-check all files formatted 0.4s
lint 24 errors, 41 warnings 7.3s
typecheck ⏭️ no tsconfig.json
unit-test ⏭️ no test script in package.json
build built local/redux_gui:ci · 235MB 60.2s
integration-test /api/health ready · 4 passed 5.8s
push ⏭️ not implemented

Overall: ❌ 3 passed · 2 failed · 3 skipped

❌ audit — 1 high
Severity Location Rule Message
high svgo@3.0.0 - 3.3.3 GHSA-2p49-hgcm-8545 SVGO removeScripts plugin leaves some executable scripts intact
❌ lint — 24 errors, 41 warnings
Severity Location Rule Message
error components/Visualization/QuantumCircuitVis.js:140 react-hooks/set-state-in-effect Error: Calling setState synchronously within an effect can trigger cascading renders
error components/hooks/ProblemProvider/Problem.js:51 no-undef 'requestInfo' is not defined.
error components/hooks/ProblemProvider/Problem.js:72 react-hooks/set-state-in-effect Error: Calling setState synchronously within an effect can trigger cascading renders
error components/hooks/ProblemProvider/Reducer.js:144 react-hooks/set-state-in-effect Error: Calling setState synchronously within an effect can trigger cascading renders
error components/hooks/ProblemProvider/Reducer.js:167 react-hooks/set-state-in-effect Error: Calling setState synchronously within an effect can trigger cascading renders
error components/hooks/ProblemProvider/Reducer.js:186 react-hooks/set-state-in-effect Error: Calling setState synchronously within an effect can trigger cascading renders
error components/hooks/ProblemProvider/Reducer.js:205 react-hooks/set-state-in-effect Error: Calling setState synchronously within an effect can trigger cascading renders
error components/hooks/ProblemProvider/Reducer.js:229 react-hooks/immutability Error: Cannot access variable before it is declared
error components/hooks/ProblemProvider/Reducer.js:233 react-hooks/set-state-in-effect Error: Calling setState synchronously within an effect can trigger cascading renders
error components/hooks/ProblemProvider/Reducer.js:62 react-hooks/set-state-in-effect Error: Calling setState synchronously within an effect can trigger cascading renders
error components/hooks/ProblemProvider/Reducer.js:86 react-hooks/set-state-in-effect Error: Calling setState synchronously within an effect can trigger cascading renders
error components/hooks/ProblemProvider/Solver.js:144 react-hooks/set-state-in-effect Error: Calling setState synchronously within an effect can trigger cascading renders
error components/hooks/ProblemProvider/Solver.js:30 react-hooks/set-state-in-effect Error: Calling setState synchronously within an effect can trigger cascading renders
error components/hooks/ProblemProvider/Verifier.js:89 react-hooks/set-state-in-effect Error: Calling setState synchronously within an effect can trigger cascading renders
error components/pageblocks/ProblemRowReact.js:169 react-hooks/set-state-in-effect Error: Calling setState synchronously within an effect can trigger cascading renders
error components/pageblocks/ProblemRowReact.js:177 react-hooks/immutability Error: This value cannot be modified
error components/pageblocks/VerifyRowReact.js:47 react-hooks/set-state-in-effect Error: Calling setState synchronously within an effect can trigger cascading renders
error components/pageblocks/VerifyRowReact.js:53 react-hooks/set-state-in-effect Error: Calling setState synchronously within an effect can trigger cascading renders
error components/pageblocks/VisualizeRowReact.js:125 react-hooks/set-state-in-effect Error: Calling setState synchronously within an effect can trigger cascading renders
error components/pageblocks/VisualizeRowReact.js:129 react-hooks/set-state-in-effect Error: Calling setState synchronously within an effect can trigger cascading renders
… and 45 more

Tools/ProblemInstanceParser.js:72 had `([\w!]+)+` — a `+`-quantified
group whose body is itself `+`-quantified. The outer `+` is redundant
(the character class already matches one-or-more) and creates
exponential backtracking on inputs like many repeated `!` characters,
flagged by CodeQL (js/redos). Dropping the outer `+` is behaviorally
identical (verified against valid/invalid sample inputs) and resolves
instantly on the adversarial input that hung the original.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01K5wXdN2yC9f8vuAuXBVCNo
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.

CI: fix format-check failures (58 format + 33 import-order)

2 participants