coderaiser / putout-editor / 36302086314

100%

push

github

docs: architecture, agents, issues: why redlint exists, and the css gate

Records the part that was missing from this repo's notes: a putout rule
deliberately knows nothing about filenames - it sees one AST - so anything that
is a statement about a tree, like colours only in tokens.css, has to be expressed
against a tree. redlint builds that tree as JSON (@putout/processor-filesystem)
and runs the rules over it. Run a rule and nothing is modified; run redlint fix
and the modifications are applied. That is why there are two kinds of rule in
packages/plugin-putout-editor and only one of them runs under `putout .`.

Also: putout is written with the full name in prose, and the css finding records
the two facts that cost time - CSS is JS, where #ff0000 is color(...) and not
hashValue, and report-only is a real option whose cost is one no-op action.

1079 of 1079 branches covered (100.0%)

Branch coverage included in aggregate %.

6646 of 6646 relevant lines covered (100.0%)

61.54 hits per line