coderaiser / putout-editor / 36325743174

100%

push

github

docs: putout: a fixture without a -fix twin is a negative case, not an orphan

putout-map.md said "a fixture never exists without its fixed twin", and putout-style.md
and the mcp style section repeated it. Checked it rather than leaving it, and it is
false: 2035 fixture files, 816 with a -fix twin, 203 without.

The 203 are not dead files. They are the cases a rule must NOT fire on, read by
t.noReport / t.noTransform, and they are named for it:

  packages/plugin-apply-overrides/test/fixture/no-overrides.js
    -> t.noReport('no-overrides')
  packages/plugin-apply-at/test/fixture/assignment.js
    -> t.noTransform('assignment')

There is nothing to fix, so there is no twin. The convention is narrower than the one I
wrote: a fixture a transform asserts on has a -fix twin, a fixture a not* asserts on
does not.

Worth writing down how the wrong claim survived, because the shape of it is the same as
the mistakes this repository keeps finding. I measured "113 of 116 plugins have fixtures
and every one has at least one -fix" - which is true - and then generalised the plugin
level to the file level without a second pass. A correct count at one grain became a
false rule at another. The check that catches it is the one that was not run: the file
count, not the directory count.

Left the correction in place rather than quietly fixing it, since "a count of fixtures
without twins looks like 203 dead files when it is 203 negative cases" is the trap.

1081 of 1081 branches covered (100.0%)

Branch coverage included in aggregate %.

6663 of 6663 relevant lines covered (100.0%)

61.54 hits per line