mirror of
https://github.com/larvit/adf-codec.git
synced 2026-11-13 04:08:29 +01:00
Hold the import boundaries in the lint config and name its script and leg lint
This commit is contained in:
+10
-5
@@ -672,13 +672,14 @@ compared against `undefined` — have a half no valid document reaches.
|
||||
|
||||
## The size ratchet
|
||||
|
||||
2026-09-20, the maintainer. KISS, a technical principle. Valid while no measure picks out what
|
||||
readers find hard better than a function's length.
|
||||
2026-09-20, the import boundaries 2026-10-22, the maintainer. KISS, a technical principle. Valid
|
||||
while no measure picks out what readers find hard better than a function's length.
|
||||
|
||||
`.oxlintrc.json`'s single rule, over the files `tsconfig.build.json` builds, is a per-function line
|
||||
`.oxlintrc.json` holds one size rule and the import boundaries of §The source parts by ADF and
|
||||
format. The size rule, over the files `tsconfig.build.json` builds, is a per-function line
|
||||
ceiling, set at that set's worst and moving only downward. It covers the built files alone, since
|
||||
one ceiling over the tests too would have to be their worst, loosening the guard over the shipped
|
||||
code. It guards against drift and never drives a refactor, so no cyclomatic rule and no second lint
|
||||
code. It guards against drift and never drives a refactor, so no cyclomatic rule and no second size
|
||||
rule join it: neither measure picked out what nine readers found hard (the comprehension panel,
|
||||
2026-09-20). `oxlint` measures it since TypeScript 7 is a native compiler publishing no in-process
|
||||
parser, only the `unstable/` AST surface an out-of-process handshake reaches. Three switches guard
|
||||
@@ -687,6 +688,9 @@ config gone missing fails the leg instead of falling back to oxlint's own defaul
|
||||
`--deny-warnings`, since a rule from a category this config never names arrives as a warning it
|
||||
exits 0 on.
|
||||
|
||||
The boundaries are `no-restricted-imports` overrides over the same files, since the technical
|
||||
principles refuse a test that scans the source and a regex misses import spellings a rule reads.
|
||||
|
||||
## The project ships under the comprehension floor until items 62 and 95 land
|
||||
|
||||
2026-10-03, the maintainer; item 95 in place of item 61, 2026-10-09, the maintainer. KISS, a
|
||||
@@ -935,4 +939,5 @@ whether a list marker interrupts a paragraph — is one function there too, neve
|
||||
direction, however conservative the copy would be. Where the rule is the emitter's own choice, input
|
||||
consults it rather than restating it, so no fixture the emitter writes can be refused, and a
|
||||
spelling the emitter refuses gives its own error rather than a second name for it. That consulting
|
||||
is the only import `parse/` takes from `emit/`, through `emit/spelling-questions.ts`.
|
||||
is the only import `parse/` takes from `emit/`, through `emit/spelling-questions.ts`. `.oxlintrc.json` holds that import, and keeps
|
||||
`markdown/directive/` from importing `emit/` or `parse/` (§The size ratchet).
|
||||
|
||||
Reference in New Issue
Block a user