coderaiser / putout-editor / 36347846070

100%

push

github

docs: issues: a fence that shows a violation gets corrected by the fixer

The press-modifier-case ❌ and ✅ pair in the plugin README were byte-identical,
because putout . --fix applied the plugin's own rule to the fence demonstrating
the violation and deleted the anti-pattern. Nothing failed: the fence is valid
JavaScript before and after, so the parser rule is satisfied and there is
nothing left to report.

Worth writing down because the generalisable failure is that a fence showing a
violation is valid code the rule rejects - the fixer's job and the example's
purpose are exactly opposed, and the fixer always wins. It is why the existing
advice to keep anti-patterns out of js/ts fences is a correctness rule rather
than a style one, and it is the concrete instance of idea 7 in docs/ideas.md.

A check that would have caught it: the rule's own fixture is the oracle, so the
README's ❌ block should equal test/fixture/<name>.js and the ✅ block
<name>-fix.js. Nothing asserts that today, which is how the two drifted apart.

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