coderaiser / putout-editor / 36328369035

100%

push

github

feature: mcp: docs style warns what the ?. fixer does not tell you

The style section said optional chaining is forbidden and that ?. narrows a type where &&
does not. Both true, both easy to nod at and then run the fixer anyway. What it did not
say is that the fixer exits 0 either way - so the warning had nothing to attach to.

Section 7 now says: run tsc after it, and look for `a && a.b` and `a() && a().b()`. The
duplicated receiver and the bare statement-position logical are the two consequences a
single-file linter can catch, and one of them is a rule in this repository now.

Two specs pin the two sentences an agent most needs - "exits 0" and "run tsc" - because
the rest of the section can be reworded, but if either of those goes, the advice stops
being actionable and starts being reassuring.

The backticks in the section are escaped, not bare: the whole section is one template
literal, and the first draft terminated it mid-string. Caught by the suite, not by reading.

150 tests.

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