You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Factor the YAML indent-region skeleton into one emitIndentRegion helper
The block-scalar (`bsKey`, `bsKey-seq`) and plain-fold (`plain-continuation`,
`plain-bare-fold`) regions each open-coded the same shape: capture the line's
leading indent with `^([ \t]*)` into `\1`, then `while: \G(?=…)` continue while a
line is blank or matches a `\1`-relative condition. That shape is the depth-bearing
"indent region" — a rule-stack frame remembering one nesting level's indent — so name
it once: `emitIndentRegion({ lookahead, cont, blankFirst?, beginCaptures?, patterns })`.
The four regions become four-line calls; `blankFirst` keeps the two families' arm
order (block scalars list `cont` first, the plain folds list blank first), so the
emitted regex is unchanged. The document-root block scalar uses a doc-marker bound,
not a `\1`-indent bound, so it stays inline.
Pure source dedup: the generated yaml.tmLanguage.json is BYTE-IDENTICAL (git diff
empty) and the other six grammars are unchanged; yaml-issue12-regressions 6 pass /
4 known-bug / 0 regression; agnostic 9/9; sanity 15/15; RedCMD Onigmo diagnostics
clean; tsc clean.
0 commit comments