You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sweep two thirds of the rubocop directives out of the code
63 rubocop:disable and enable markers become 22, all three ways.
Whole-file judgments move into .rubocop.yml, justification and all:
the Metrics exemptions for the one-concern homes (Production,
CoverageViolations, the usage document, the location conventions, the
viewer-data validator, the sandbox harness, the dogfood report), the
Naming/PredicateMethod allowance for commands that report whether
they acted, the class-variable fakes that mirror Minitest's own flag,
and the behavior-describing specs no single class owns. Fixtures are
now excluded wholesale as the byte-stable inputs they are, which
retires their inline markers and the per-fixture exclusion list. The
two directive lines inside fixtures become plain comments rather than
disappearing, so the line numbers the specs assert against stay put.
Two sites are refactored instead: the RSpec stand-ins in the test
tracker spec become verified class and instance doubles, and the
shadowing inspect's unused parameter gains its underscore.
What remains inline is the deliberate minimum, each with its reason:
Marshal on our own pipes, stderr that must not be warn, the literal
/dev/null of a git diff, evals whose foreign location is the point,
and their kin.
0 commit comments