Repository navigation
Conversation
The variable is already declared with var in the same function, so the repeat only assigns.
Each was assigned without let/var, creating a global, but is only used within the function (or loop) that assigns it, and is not used by any other script on the page, so let does not change behaviour.
It was an implicit global, used only inside its for...of loop.
PID_H_TOT and TGT_FILT_H are set in both branches and read after them; H_att_nff_pred was the one destructured name missing from the var list above it. All were implicit globals used only in their function.
|
I think we should probably wait for #337 to go in. |
|
Yes that would be most appreciated. |
|
sounds good! can you drop a note here once merged so i can update accordingly if necessary? |
Previous review (2026-11-09)Automated review note — AI-generated (Claude+Codex), validated against the live diff. Please sanity-check before acting. Reviewed at head This is a behaviour-neutral ESLint cleanup of AnalyticTune. The lint result and the base/head output equivalence both check out at this head, and only one small commit-message fix is suggested. Should fix
Note
The suggestion to hoist the |
dbl and triple in the notch filter were implicit globals that nothing read; declaring them only made them unused locals. Drop them and prune their suppressions.
bd8dbb3 to
a7c2699
Compare
|
Automated review note — AI-generated (Claude+Codex), validated against the live diff. Please sanity-check before acting. Reviewed at head This is a behaviour-neutral ESLint cleanup of AnalyticTune. Lint and the base/head output comparisons check out at a7c2699, and nothing needs changing. Note
The earlier |
Fixes ESLint problems in AnalyticTune and removes the fixed entries from
eslint-suppressions.json. None of the changes alter behaviour.dblandtriplein the notch filters were implicit globals that nothing read; declaring them would only make them unused locals, so they are removed.One commit per kind of fix;
npm run lintpasses.