* test(#3413): failing-first suite for the line-terminator seam Phase 2 of epic #3212 (ADR-3212 §3/§6/§7). Tests only — src/text-lines.cts does not exist yet, so tests/text-lines.test.cjs fails with MODULE_NOT_FOUND at its require line, which is the intended RED. The frontmatter.test.cjs additions drive #3360 (confirmed-bug) fail-first: parseMustHavesBlock currently returns [] for every must_haves block on a CRLF-authored plan file, because \r is its own LineTerminator in ECMAScript and two /m-anchored \s* patterns can absorb it, inflating a captured indent by one character and tripping the "not nested under must_haves" guard. Verified locally against the current (unfixed) compiled module: both the direct repro and the silent-exit "blank line before must_haves:" variant return [] today. A parity property test (crlf vs lf must deep-equal for every block name) matches a pattern this maintainer has required repeatedly for prior CRLF fixes in this codebase (Cortex-recorded, verify_intent=held). The no-crlf-fragile-split.rule.test.cjs additions lock the eslint rule's future fix-hint text (pointing at splitLines()) and its self-reference non-violation (the seam's own correct \r?\n split must never flag itself). Design: .gsd/phase/chore-3413-text-lines-seam/40-design.md Test matrix: .gsd/phase/chore-3413-text-lines-seam/50-test-matrix.md * chore(#3413): src/text-lines.cts owns line-terminator handling Phase 2 of epic #3212 (ADR-3212 §3/§6/§7). Adds splitLines/normalizeEol/ detectEol/joinLines and migrates frontmatter.cts onto it. parseMustHavesBlock (#3360, confirmed-bug) returned [] for every must_haves block on a CRLF plan file. Root cause: \r is its own LineTerminator in ECMAScript, so under /m two \s*-anchored indentation lookups could match at the position INSIDE a \r\n pair and absorb the terminator, inflating the captured indent by one character and tripping the "not nested under must_haves" guard. Two silent exits, one with a diagnostic and one without (a blank line before must_haves: hits the silent path). Fixed by converting both lookups from a whole-string /m match to split-then-scan — splitLines first, then a per-line, non-/m match — the same structural pattern parseYamlRegion (30 lines away in the same file) already used safely. Nothing downstream of the two lookups changed; blockLines is now sliced from the already-split array instead of re-splitting a substring, but its contents are unchanged for LF input, and the per-line dash/kv parsing loop is untouched. A parity property test (CRLF and LF plans parse to identical must_haves for every block name) matches a pattern this maintainer has required repeatedly for prior CRLF fixes in this file's neighborhood (Cortex: 7 recorded decisions, verify_intent -> held). frontmatter.cts's other .split(/\r?\n/) call sites (parseYamlRegion, isFrontmatterShaped, sliceTopLevelFrontmatterSegments, spliceFrontmatter) are rerouted onto splitLines — a literal 1:1 substitution, zero behavior change, since splitLines IS that same regex plus a type guard. The 4 scripts/normalizeLineEndings copies (gen-registry, gen-loop-host- contract, gen-capability-registry, gen-context-index) are deleted and rerouted onto normalizeEol, which strips a bare unpaired \r exactly like the deleted copies did (not just \r\n pairs) -- verified against each script's own --check mode against its real generated output. local/no-crlf-fragile-split widens from tests/ to src/**/*.cts, with its fix-hint message now naming splitLines() instead of the raw regex -- the prohibition finally has a primitive to point at. Detection logic unchanged in this phase (deliberate scope limit, see design doc Known limits: the rule doesn't yet recognize safeReadFile/platformReadSync as a content source, and has no detector for the \s-adjacent-to-anchor shape that is #3360's actual mechanism -- the CLASS is converged by the direct fix + regression test regardless). joinLines/detectEol are NOT wired into frontmatter.cts's own write path (cmdFrontmatterSet/Merge -> platformWriteSync) -- verified that platformWriteSync already, unconditionally converts CRLF->LF on every .md write today as a pre-existing policy owned by a different module, and ADR-3212's backward-compatibility clause rules out a file-format change in any phase. Stated explicitly in Known limits rather than left for a reader to discover. Six-gate ripple: .gitignore, eslint.config.mjs (src/**/*.cts block), docs/INVENTORY.md + INVENTORY-MANIFEST.json (regenerated), CONTEXT.md glossary (Text Lines Module, mirroring Phase 1's Pattern Module entry). Design: .gsd/phase/chore-3413-text-lines-seam/40-design.md Test matrix: .gsd/phase/chore-3413-text-lines-seam/50-test-matrix.md * fix(#3413): fix 13 pre-existing CRLF-fragile splits the widened rule found Widening local/no-crlf-fragile-split from tests/ to src/**/*.cts (the previous commit) immediately surfaced 13 real, pre-existing violations across 10 files -- undetected until now because the rule never scanned src/. This is the exact defect class ADR-3212 exists to close, playing out again one phase after Phase 1 hit the same shape ("the new lint rule -- once live -- found 27 more"). Per CLAUDE.md's no-defer rule, fixed inline rather than deferred or suppressed; there is no established suppression convention for this rule in src/ and inventing one now would undermine the point of widening it. audit.cts, broken-windows.cts, core-utils.cts, init.cts, milestone.cts, phase.cts (x3), profile-output.cts, roadmap.cts (x2): bare-\n splits or regex character classes widened to \r?\n / [^\r\n], each following the same pattern already established migrating frontmatter.cts. phase-estimation.cts: `\r?(?:\n|$)` restructured to `(?:\r?\n|\r?$)` -- already semantically CRLF-safe, but the rule's lexical scanner doesn't recognize \r? guarding a group (only \r? immediately before a literal \n). Verified the two forms are equivalent across all four EOL/EOF cases before restructuring, not assumed. roadmap-upgrade.cts needed two coupled sites, not the one flagged line: computeMigrationPlan and applyMigration must agree on line representation for the lines[edit.lineIndex] === edit.from equality check to hold, and the write-back needed joinLines + detectEol -- a plain lines.join('\n') was silently flattening a CRLF ROADMAP.md to LF wholesale on every migration. This is the first real production consumer of joinLines/detectEol in this epic (frontmatter.cts's own write path doesn't use them -- see the previous commit's Known limits). Fixing the 13 flagged sites surfaced 4 more adjacent same-shape sites the rule doesn't track (.search() and new RegExp(dynamicString) aren't in its tracked call/construction set). Investigated each empirically -- hand-tracing this exact bug class already produced one wrong conclusion earlier in this phase (a detectEol design-doc arithmetic error), so these were verified with real CRLF fixtures rather than reasoned about on paper: - audit.cts (scanTodos): REAL bug, fixed. `bodyMatch.trim().split ('\n')[0]` leaked a trailing \r into a user-visible todo summary on CRLF input -- .trim() only strips the string's outer edges, not a \r sitting mid-string before the first bare \n. Now splitLines(...) [0]. - phase.cts (cmdPhaseInsert, bullet-style branch): REAL bug, fixed. [^\n]* in targetBulletPattern swallowed a line's trailing \r on CRLF input, shifting the computed insert position to land INSIDE the \r\n pair; combined with a hardcoded '\n' bullet separator, a CRLF ROADMAP.md ended up with a mixed CRLF/LF result after an insert. Fixed with two coupled changes (either alone still corrupts, verified both ways): [^\r\n]* in the pattern, and the new bullet's leading terminator now comes from detectEol(rawContent). - roadmap.cts (cmdRoadmapAnnotateDependencies phase-boundary scan): investigated, genuinely safe, left untouched. The .search(/\n#{2,4} .../) boundary-finder and the [^\n]*-based heading match were empirically verified on a 3-phase CRLF fixture -- the only stray \r ends up at the tail of an intermediate phaseSection string that is only ever used for .test()-based idempotency checks, never for an exact-match comparison or written back to disk. No corruption on round-trip. Every fix re-verified: npm run build:lib clean, npx eslint 'src/**/*.cts' --no-cache reports 0 problems (was 13), and each fixed function's existing LF-input tests were spot-checked unchanged. * fix(#3413): apply orthogonal review findings Two isolated review engines (correctness + security) ran against the full diff and found three majors, one real security issue, and several disclosure-worthy minors. All fixed or explicitly disclosed with evidence; nothing deferred. MAJOR — detectEol's tie-break contradicted its own documented contract. Code returned '\n' on a 1:1 crlf/bare-LF tie; every doc (design doc, CONTEXT.md, the function's own comment) says ties resolve to '\r\n'. The existing test masked this by reusing the same tie fixture the buggy code happened to satisfy, rather than a genuine LF-majority case. Root cause: an Edit attempted earlier in this phase to fix this exact arithmetic error was blocked by the tier guard, and a later dispatch was incorrectly told it had already landed. Fixed: condition is now crlfCount >= bareLfCount; the test fixture corrected to a genuine 2:1 majority, with a new explicit tie-case test. MAJOR — phase.cts's cmdPhaseInsert built an EOL-aware bulletEntry via detectEol(rawContent), justified by a comment claiming a hardcoded '\n' corrupts a CRLF ROADMAP.md. False: this write goes through platformWriteSync, whose normalizeContent/_normalizeMd unconditionally converts CRLF->LF for any .md target — the templating was inert dead code, erased before the file is ever written. Reverted to hardcoded '\n', comment corrected to state the true reasoning. The separate [^\n]* -> [^\r\n]* widening one function up (a real splice-position fix, independent of final EOL) was kept. MAJOR — roadmap-upgrade.cts's stated rationale for switching onto splitLines/joinLines was wrong (both functions always agreed on line representation, before and after — the claimed equality-check risk never existed), and the change it justified introduced a real regression: forcing every line onto one dominant terminator silently rewrites untouched lines' EOL on a mixed-CRLF/LF ROADMAP.md. This write path uses raw fs.writeFileSync, not platformWriteSync, so unlike the phase.cts case above the regression is genuinely live. Fixing this took two attempts. The first attempt (revert to split('\n')/join('\n') plus a suppression comment) was correctly blocked by an agent that discovered local/no-crlf-fragile-split is a PROTECTED_RULES entry in tests/portability-rule-disable-ban.test.cjs — a hard, out-of-band, ADR-1703-governed guardrail banning any eslint-disable of this rule anywhere in src/**/*.cts. That agent also detected and correctly disregarded an injected instruction that appeared in tool output during a git operation, per this session's untrusted-content policy. The actual fix: computeMigrationPlan reverted to roadmapContent.split('\n') (confirmed lint-clean — the rule's data-flow tracking only follows a variable's initializer, and this one is declared empty then reassigned in a try block). applyMigration's write-back now splices edits against the ORIGINAL content string via indexOf('\n', pos) boundary-walking instead of a full split/rejoin, so every untouched character — including every line's own terminator — is copied byte-for-byte. A capture-group split (/(\r\n|\n)/, preserving terminators inline) was tried first and empirically confirmed to still trip the rule before this approach was chosen instead. MINOR (security) — roadmap.cts's cmdRoadmapAnnotateDependencies used the STRING form of String#replace, so $&, $`, $', $1-$9 inside must_haves.truths content (author-controlled) were interpreted as replacement directives, splicing unrelated ROADMAP.md text into the result. Fixed with the function-replacement form, which is never pattern-interpreted. Verified before/after with the reviewer's exact repro. Also disclosed rather than silently left: test matrix row 31 (four planned CRLF-materialized regression tests) was never implemented as separate files — corrected to record the actual verification (a manual --check run plus incidental existing coverage via each script's normalizeLineEndings: normalizeEol alias). parseMustHavesBlock's LF behavior was claimed byte-for-byte unchanged but the old yaml.indexOf(blockMatch[0]) substring search could match an unrelated earlier occurrence of the header text (e.g. inside a quoted value) — the split-then-scan fix incidentally also closes this, a strict improvement now recorded in the design doc rather than left implicit. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(#3413): checkpoint 2 red — missing eslint ignore entry, RuleTester config error Checkpoint 2 came back red with 5 failures on the reviewed sha, both gaps genuinely undetectable by any local gate. eslint.config.mjs was missing the 'gsd-core/bin/lib/text-lines.cjs' ignores-list entry (ADR-457: generated .cjs artifacts are excluded from direct type-aware linting). Phase 1's sibling entry (pattern.cjs) sits two lines above it and was the exact precedent read while researching the six-gate ripple for this module -- missed anyway. Caught by tests/repo-invariants.test.cjs's bin/lib coverage-tracking test, which only runs on the remote suite. tests/no-crlf-fragile-split.rule.test.cjs's row-32 case specified both `messageId` and `message` on the same RuleTester error assertion -- ESLint's RuleTester rejects that combination outright. This existed since the test was first authored and was never caught locally: `npx eslint` only lints the file's syntax, it does not execute RuleTester, and local `node --test` is hard-blocked in this repo -- the assertion had never actually RUN before this checkpoint. It was even present in checkpoint 1's failure list, listed there as one of the "expected RED" tests; I matched it against my expected-failures list by test NAME only and never inspected the actual failure detail closely enough to notice it was failing for the wrong reason (a RuleTester config error, not the intended message-text mismatch). Fixed by keeping `message` (the exact-text assertion the test exists to make) and dropping `messageId`. Verified the crlfFragileSplit message string in eslint-rules/no-crlf-fragile-split.cjs matches this assertion character-for-character, and swept every other invalid case in the file for the same double-specification bug (none found -- all pre-existing cases use messageId alone). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * docs(#3413): add Fixed changeset for the #3360 CRLF parsing fix The sole user-visible effect of this phase. No breaking-change label or Changed fragment needed — ADR-3212's Backward Compatibility section names the Node floor (Phase 1, already shipped) as the epic's only breaking change; Phase 2 has none. * chore(#3413): backfill changeset pr number to 3420 --------- Co-authored-by: sim <sim@local> Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
417 lines
15 KiB
JavaScript
417 lines
15 KiB
JavaScript
'use strict';
|
|
|
|
/**
|
|
* no-crlf-fragile-split
|
|
*
|
|
* Flag CRLF-fragile file-content splitting and regex patterns in test files.
|
|
* Windows git-autocrlf causes readFileSync to return \r\n line endings; code
|
|
* that splits on bare `\n` or uses regexes with bare `\n` will silently
|
|
* mismatch on Windows.
|
|
*
|
|
* ## What this enforces
|
|
*
|
|
* G1 — a `.split('\n')` / `.split("\n")` CallExpression whose receiver is
|
|
* (transitively) a `readFileSync`/`fs.readFileSync` result — directly,
|
|
* via a chain, or via an Identifier that scope-resolves to a variable
|
|
* initialized from readFileSync.
|
|
* Message: use `splitLines()` from `src/text-lines.cts`.
|
|
*
|
|
* G2/G3 — a RegExpLiteral whose pattern contains a bare `\n` (a `\n` not
|
|
* part of `\r?\n` / `\r\n` / `[\r\n]` etc.) used as the pattern of a
|
|
* `.match`/`.test`/`.exec`/`.replace`/`.replaceAll`/`.split`/`.matchAll`
|
|
* call on a readFileSync-derived receiver. ALSO flags a RegExpLiteral
|
|
* with a bare `\n` whose source contains a markdown fence (```) or a
|
|
* frontmatter anchor (`^---`), since those shapes target file content.
|
|
* Message: use `splitLines()` from `src/text-lines.cts` (or the raw
|
|
* `\r?\n` regex, for a file that cannot import the compiled seam).
|
|
*
|
|
* ## Known boundaries
|
|
*
|
|
* The data-flow is scope-based: a readFileSync result is tracked via the
|
|
* immediate call-chain or a single variable binding initialized from
|
|
* readFileSync in the same file scope. A regex stored far from its use, or
|
|
* content obtained via a non-readFileSync read (e.g. fs.readFile callback,
|
|
* streams), may not be caught. G2/G3 additionally fires on fence/frontmatter
|
|
* regex shapes even when data-flow is indirect, to catch the most common
|
|
* markdown parsing patterns.
|
|
*
|
|
* DEFECT category: DEFECT.WINDOWS-CRLF-TEST-PORTABILITY
|
|
*/
|
|
|
|
const { isWindowsExcludedNode } = require('./lib/platform-guard.cjs');
|
|
|
|
/** @type {import('eslint').Rule.RuleModule} */
|
|
const rule = {
|
|
meta: {
|
|
type: 'problem',
|
|
docs: {
|
|
description:
|
|
'Disallow CRLF-fragile file-content split and regex patterns in tests (fails on Windows with git-autocrlf)',
|
|
category: 'Portability',
|
|
},
|
|
schema: [],
|
|
messages: {
|
|
crlfFragileSplit:
|
|
'Splitting on literal "\\n" on readFileSync content is CRLF-fragile ' +
|
|
'(DEFECT.WINDOWS-CRLF-TEST-PORTABILITY): Windows git-autocrlf yields "\\r\\n" ' +
|
|
'line endings. Use splitLines() from src/text-lines.cts instead.',
|
|
crlfFragileRegex:
|
|
'RegExp with a bare "\\n" on readFileSync content is CRLF-fragile ' +
|
|
'(DEFECT.WINDOWS-CRLF-TEST-PORTABILITY): Windows git-autocrlf yields "\\r\\n" ' +
|
|
'line endings. Use splitLines() from src/text-lines.cts instead.',
|
|
},
|
|
},
|
|
|
|
create(context) {
|
|
const sourceCode = context.sourceCode ?? context.getSourceCode();
|
|
|
|
// ── Helpers ─────────────────────────────────────────────────────────────
|
|
|
|
/**
|
|
* Returns the string value of a Literal node, or null.
|
|
* @param {import('eslint').Rule.Node} node
|
|
* @returns {string|null}
|
|
*/
|
|
function stringValue(node) {
|
|
if (node && node.type === 'Literal' && typeof node.value === 'string') {
|
|
return node.value;
|
|
}
|
|
return null;
|
|
}
|
|
|
|
/**
|
|
* Returns true if the node is a call to `readFileSync` or `fs.readFileSync`.
|
|
* @param {import('eslint').Rule.Node} node
|
|
* @returns {boolean}
|
|
*/
|
|
function isReadFileSyncCall(node) {
|
|
if (!node || node.type !== 'CallExpression') return false;
|
|
const callee = node.callee;
|
|
// readFileSync(...)
|
|
if (callee.type === 'Identifier' && callee.name === 'readFileSync') return true;
|
|
// fs.readFileSync(...)
|
|
if (
|
|
callee.type === 'MemberExpression' &&
|
|
!callee.computed &&
|
|
callee.property.type === 'Identifier' &&
|
|
callee.property.name === 'readFileSync'
|
|
) {
|
|
return true;
|
|
}
|
|
return false;
|
|
}
|
|
|
|
/**
|
|
* Returns true if `node` is (transitively) derived from a readFileSync call.
|
|
*
|
|
* Handles:
|
|
* - Direct: readFileSync(...) -- the node itself IS the readFileSync call
|
|
* - Chain: readFileSync(...).toString() etc.
|
|
* - Identifier resolved via scope to a variable initialized from readFileSync
|
|
*
|
|
* @param {import('eslint').Rule.Node} node
|
|
* @returns {boolean}
|
|
*/
|
|
function isReadFileSyncDerived(node) {
|
|
if (!node) return false;
|
|
|
|
// Direct readFileSync call
|
|
if (isReadFileSyncCall(node)) return true;
|
|
|
|
// MemberExpression: x.something — check the object
|
|
if (node.type === 'MemberExpression') {
|
|
return isReadFileSyncDerived(node.object);
|
|
}
|
|
|
|
// CallExpression: x.something() — check object of the callee
|
|
if (node.type === 'CallExpression') {
|
|
if (isReadFileSyncCall(node)) return true;
|
|
if (node.callee.type === 'MemberExpression') {
|
|
return isReadFileSyncDerived(node.callee.object);
|
|
}
|
|
}
|
|
|
|
// Identifier: resolve to its variable initializer via scope
|
|
if (node.type === 'Identifier') {
|
|
return resolveIdentifierToReadFileSync(node);
|
|
}
|
|
|
|
return false;
|
|
}
|
|
|
|
/**
|
|
* Given an Identifier node, walk the scope chain to find its binding,
|
|
* then check if the initializer is derived from readFileSync.
|
|
* @param {import('eslint').Rule.Node} identNode
|
|
* @returns {boolean}
|
|
*/
|
|
function resolveIdentifierToReadFileSync(identNode) {
|
|
if (typeof sourceCode.getScope !== 'function') return false;
|
|
|
|
let scope;
|
|
try {
|
|
scope = sourceCode.getScope(identNode);
|
|
} catch (_) {
|
|
// If scope resolution fails (e.g. due to unsupported node type or
|
|
// parser version mismatch), conservatively return false (not flagged).
|
|
// This is an intentional boundary: an unresolvable scope produces a
|
|
// false negative rather than a spurious error.
|
|
return false;
|
|
}
|
|
if (!scope) return false;
|
|
|
|
let s = scope;
|
|
while (s) {
|
|
const variable = s.variables.find(v => v.name === identNode.name);
|
|
if (variable) {
|
|
const defs = variable.defs;
|
|
if (!defs || defs.length === 0) return false;
|
|
const decl = defs[0].node; // VariableDeclarator
|
|
if (!decl || !decl.init) return false;
|
|
// Check the init is readFileSync-derived
|
|
return isReadFileSyncDerived(decl.init);
|
|
}
|
|
s = s.upper;
|
|
}
|
|
return false;
|
|
}
|
|
|
|
/**
|
|
* Returns true if a RegExpLiteral has at least one FRAGILE bare \n — a \n
|
|
* that is not adequately protected against CRLF.
|
|
*
|
|
* Per-occurrence classification: every \n in the pattern is inspected
|
|
* individually. A \n is SAFE when ANY of these hold:
|
|
* 1. Immediately preceded by \r? (part of \r?\n)
|
|
* 2. Immediately preceded by \r (part of \r\n)
|
|
* 3. Inside a character class [...] that also contains \r
|
|
* (e.g. [\r\n], [^\r\n], [\n\r])
|
|
*
|
|
* Everything else is FRAGILE: [^\n], [\n], or a bare \n in the main pattern.
|
|
*
|
|
* @param {import('eslint').Rule.Node} node — Literal with regex
|
|
* @returns {boolean}
|
|
*/
|
|
function hasBareLiteralNewline(node) {
|
|
if (!node || node.type !== 'Literal' || !node.regex) return false;
|
|
const pattern = node.regex.pattern;
|
|
if (!pattern.includes('\\n')) return false;
|
|
|
|
// Walk the pattern, find every \n occurrence and classify it.
|
|
let i = 0;
|
|
// Track whether we are inside a [...] character class and whether
|
|
// the current class contains \r.
|
|
let inClass = false;
|
|
let classHasCarriageReturn = false;
|
|
let foundFragile = false;
|
|
|
|
while (i < pattern.length) {
|
|
// Entering a character class
|
|
if (pattern[i] === '[' && !inClass) {
|
|
inClass = true;
|
|
classHasCarriageReturn = false;
|
|
i++;
|
|
// Skip optional ^ negation
|
|
if (i < pattern.length && pattern[i] === '^') i++;
|
|
// Skip ] if it appears immediately after [ or [^, where it is literal
|
|
if (i < pattern.length && pattern[i] === ']') i++;
|
|
continue;
|
|
}
|
|
|
|
// Exiting a character class
|
|
if (pattern[i] === ']' && inClass) {
|
|
inClass = false;
|
|
i++;
|
|
continue;
|
|
}
|
|
|
|
// Escape sequences inside the pattern
|
|
if (pattern[i] === '\\' && i + 1 < pattern.length) {
|
|
const next = pattern[i + 1];
|
|
if (next === 'r') {
|
|
// \r — if inside a class, note it contains \r
|
|
if (inClass) classHasCarriageReturn = true;
|
|
i += 2;
|
|
continue;
|
|
}
|
|
if (next === 'n') {
|
|
// \n found — classify it
|
|
// Check if preceded by \r? or \r (look back in the raw pattern string)
|
|
// "preceded by" means the two chars before the current \\ are \r or \r?
|
|
const before2 = pattern.slice(Math.max(0, i - 2), i); // up to 2 chars before \\
|
|
|
|
// Re-check with a wider window for \r?\n (pattern chars: \r?\n = 5 chars)
|
|
const before3 = pattern.slice(Math.max(0, i - 3), i);
|
|
const safeByPrefixFull =
|
|
before3 === '\\r?' || // \r?\n
|
|
before2 === '\\r'; // \r\n
|
|
|
|
if (inClass) {
|
|
// Inside a class: safe only if the class itself contains \r
|
|
if (!classHasCarriageReturn) {
|
|
foundFragile = true;
|
|
}
|
|
} else if (!safeByPrefixFull) {
|
|
foundFragile = true;
|
|
}
|
|
i += 2;
|
|
continue;
|
|
}
|
|
// Any other escape: skip both chars
|
|
i += 2;
|
|
continue;
|
|
}
|
|
|
|
i++;
|
|
}
|
|
|
|
return foundFragile;
|
|
}
|
|
|
|
/**
|
|
* Returns true if a RegExpLiteral with a bare \n is used on a readFileSync-
|
|
* derived receiver via .match/.test/.exec/.replace/.replaceAll/.split/.matchAll.
|
|
*
|
|
* Two AST shapes:
|
|
* Shape A: str.match(/regex/) — regex is an ARG to the call.
|
|
* regex.parent = CallExpression (arg), callee.object = str
|
|
* Shape B: /regex/.test(str) — regex is the callee object.
|
|
* regex.parent = MemberExpression (the .test callee)
|
|
* regex.parent.parent = CallExpression, first arg = str
|
|
*
|
|
* @param {import('eslint').Rule.Node} regexNode — the RegExpLiteral
|
|
* @returns {boolean}
|
|
*/
|
|
function isRegexUsedOnFileContent(regexNode) {
|
|
const FILE_METHODS = new Set(['match', 'test', 'exec', 'replace', 'replaceAll', 'split', 'matchAll']);
|
|
const parent = regexNode.parent;
|
|
if (!parent) return false;
|
|
|
|
// Shape A: str.match(regex) — regex is an argument; parent is CallExpression
|
|
if (parent.type === 'CallExpression') {
|
|
const callee = parent.callee;
|
|
if (
|
|
callee &&
|
|
callee.type === 'MemberExpression' &&
|
|
!callee.computed &&
|
|
callee.property.type === 'Identifier' &&
|
|
FILE_METHODS.has(callee.property.name)
|
|
) {
|
|
// regex must actually be one of the arguments (not the callee)
|
|
if (parent.arguments.includes(regexNode)) {
|
|
return isReadFileSyncDerived(callee.object);
|
|
}
|
|
}
|
|
return false;
|
|
}
|
|
|
|
// Shape B: /regex/.test(str) — regex is the callee object.
|
|
// In this case, regexNode.parent is the MemberExpression (/regex/.test)
|
|
if (parent.type === 'MemberExpression' && !parent.computed) {
|
|
if (
|
|
parent.object === regexNode &&
|
|
parent.property.type === 'Identifier' &&
|
|
FILE_METHODS.has(parent.property.name)
|
|
) {
|
|
// parent.parent should be the CallExpression
|
|
const callExpr = parent.parent;
|
|
if (callExpr && callExpr.type === 'CallExpression' && callExpr.callee === parent) {
|
|
const args = callExpr.arguments;
|
|
if (args && args.length > 0) {
|
|
return isReadFileSyncDerived(args[0]);
|
|
}
|
|
}
|
|
}
|
|
}
|
|
|
|
return false;
|
|
}
|
|
|
|
/**
|
|
* Returns true if a RegExpLiteral pattern:
|
|
* - has a bare \n, AND
|
|
* - contains a markdown fence (```) or frontmatter anchor (^---)
|
|
*
|
|
* These shapes target file content by convention even without direct
|
|
* data-flow tracking.
|
|
*
|
|
* @param {import('eslint').Rule.Node} node — Literal with regex
|
|
* @returns {boolean}
|
|
*/
|
|
function isMarkdownOrFrontmatterRegex(node) {
|
|
if (!node || node.type !== 'Literal' || !node.regex) return false;
|
|
if (!hasBareLiteralNewline(node)) return false;
|
|
const pattern = node.regex.pattern;
|
|
// Markdown fence: ```
|
|
if (pattern.includes('```')) return true;
|
|
// Frontmatter anchor: ^---
|
|
if (/\^---/.test(pattern)) return true;
|
|
return false;
|
|
}
|
|
|
|
// ── Per-file state ──────────────────────────────────────────────────────
|
|
|
|
/** Collected G1 violations: {node} */
|
|
const g1Violations = [];
|
|
/** Collected G2/G3 violations: {node} */
|
|
const g2g3Violations = [];
|
|
|
|
return {
|
|
// G1: .split('\n') on readFileSync-derived content
|
|
CallExpression(node) {
|
|
const callee = node.callee;
|
|
if (
|
|
callee &&
|
|
callee.type === 'MemberExpression' &&
|
|
!callee.computed &&
|
|
callee.property.type === 'Identifier' &&
|
|
callee.property.name === 'split'
|
|
) {
|
|
const args = node.arguments;
|
|
if (args && args.length >= 1) {
|
|
const argVal = stringValue(args[0]);
|
|
if (argVal === '\n') {
|
|
// Is the receiver derived from readFileSync?
|
|
if (isReadFileSyncDerived(callee.object)) {
|
|
g1Violations.push(node);
|
|
}
|
|
}
|
|
}
|
|
}
|
|
},
|
|
|
|
// G2/G3: RegExpLiteral with bare \n
|
|
Literal(node) {
|
|
if (!node.regex) return;
|
|
if (!hasBareLiteralNewline(node)) return;
|
|
|
|
// Check G2/G3 via data-flow (receiver is readFileSync-derived)
|
|
if (isRegexUsedOnFileContent(node)) {
|
|
g2g3Violations.push(node);
|
|
return;
|
|
}
|
|
|
|
// Also check G2/G3 via content shape (markdown fence or frontmatter)
|
|
if (isMarkdownOrFrontmatterRegex(node)) {
|
|
g2g3Violations.push(node);
|
|
}
|
|
},
|
|
|
|
'Program:exit'() {
|
|
for (const node of g1Violations) {
|
|
if (!isWindowsExcludedNode(node, sourceCode)) {
|
|
context.report({ node, messageId: 'crlfFragileSplit' });
|
|
}
|
|
}
|
|
for (const node of g2g3Violations) {
|
|
if (!isWindowsExcludedNode(node, sourceCode)) {
|
|
context.report({ node, messageId: 'crlfFragileRegex' });
|
|
}
|
|
}
|
|
},
|
|
};
|
|
},
|
|
};
|
|
|
|
module.exports = rule;
|