Linted the 10,242‑line quality gate itself
Brought 10,242 lines of quality‑gate JavaScript under a formatter
and a linter after establishing it was the largest body of code in
the repository and the only one nothing read, fixing 13 findings and
suppressing none.
July 2026

Situation. The site's quality gate is thirty‑two scripts totalling
10,242 lines of JavaScript. It was, by a wide margin, the largest
body of code in the repository, and it was the only body of code
nothing read — no formatter, no linter, no type checking. The
programs enforcing every rule in the project were the only programs
subject to none of them.

Task. The checkers had to be held to the standard they exist to
enforce, and the formatter had to be fitted to them rather than the
other way around.

Action. The formatter came first, and the indentation width was the
interesting decision. The repository's default is four spaces; at
four spaces the formatter would have rewritten 2,173 lines of the
largest checker. An override to two spaces for those files reduced
that to 38 lines of genuine drift. The principle recorded with it is
that the formatter is fitted to the code, not the code to the
formatter — reformatting two thousand lines to satisfy a preference
destroys the ability to read the history of the file. Then the
linter, which produced thirteen real findings, all fixed and none
suppressed. The Python checkers got the same treatment through a
type checker configured at a middle strictness with thirty
individual strict‑tier rules enabled on top, chosen by measurement:
at that setting the tree is silent, and of the thirty candidates
twenty‑nine were already silent and one fired — and that one was
fixed rather than exempted. The type checker found two real defects
the linter had passed clean, both about a value's shape rather than
its syntax.

Result. The largest and most load‑bearing code in the repository is
now formatted, linted and type‑checked, with thirteen findings fixed
and zero suppressions. The reason it matters more than the line
count suggests is stated in the plan: a defect in the site's
stylesheet shows up as a page that looks wrong, and a defect in a
checker shows up as a check that passes when it should not.

Categories:
1Frontend Engineering	/categories/frontend/	engineer.company	70
1DevOps	/categories/devops/	engineer.company	70
1Automation & CI/CD	/categories/automation/	engineer.company	70
1Testing & QA	/categories/testing/	engineer.company	70
1Python	/categories/python/	engineer.company	70
1Documentation	/categories/documentation/	engineer.company	70

Services:
1Frontend Development	/services/frontend-development/	engineer.company	70
1DevOps & CI/CD Automation	/services/devops-cicd/	engineer.company	70
1Technical Leadership & Consulting	/services/technical-leadership/	engineer.company	70

hThis page on the web	URL:https://engineer.company/portfolio/linted-the-10242-line-quality-gate-itself/	engineer.company	70
