3.1.0 (e05416f) shipped Reporter.withoutCache() as the per-diagnostic opt-out for findings whose correctness depends on inputs the cache doesn't track. Dropping it in 47f5410 silently broke any rule that relied on it — the call site would hit a TypeError at runtime, or fail to type-check if written in TS. Restore the API with semantics that match the original: - Diagnostic is still returned for the current run. - cache-flow filters it out before serialising the rule entry to disk, so the next warm hit on this file won't replay it (rule has to re-run to surface it again). Marker is a Symbol.for('@tsslint/no-cache') stamped on the diagnostic in core. Symbol-keyed → invisible to JSON.stringify and to {...spread}, so it doesn't leak into the on-disk cache. Test 17 covers that explicitly. README's "Caching" section is rewritten to describe the new two-layer model and explain when withoutCache() still makes sense (external inputs / fs-driven side reads); for cross-file types, the recommended path is to read ctx.program once so layer 2 handles invalidation. Tests: - cache-flow.test #15: marked diagnostic returned but not persisted - cache-flow.test #16: warm replay drops the marked one - cache-flow.test #17: marker doesn't leak through serialisation

GET https://registry.npmjs.org/tsslint - Not found #16

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions