1 Commits (fix/dev-restart-resilience)

Author	SHA1	Message	Date
Divyansh Singh	b303dd341d	feat(markdown): add region marker engine ... Shared engine for VS Code-style region extraction, used by the snippet and include rewrites. Compared to findRegion in the snippet plugin, it returns all same-named regions in document order and matches marker styles per line instead of locking onto the first style found, so same-named regions in mixed-comment files (e.g. Vue SFCs) merge. All open regions are tracked, and an end marker without a name closes the innermost region opened in its own comment style, so it neither gets captured by a region of another language nested inside it nor closes one that was left open there. The marker regexes follow the folding.markers definitions VS Code ships per language, which corrects two of the previous ones: REM is case-insensitive in bat, and #pragma allows a space after the hash. Those definitions disagree about whether the hash is required - the marker makes it optional for js and markdown, while html, css, sql, bat and f# require it - so related comment styles are merged into one regex each, keeping the hash optional only where at least one of the merged languages makes it optional. Since a markdown renderer cannot know the language of an imported file, all styles are tried on every file, which makes this a superset of what an editor folds. Note that a language service can disagree with the marker its language ships: TypeScript requires the hash the ts/js marker makes optional, while the Lua one accepts it hash-less where we require it. Fixtures covering the marker forms per language live in brc-dd/region-marker-fixtures. Quoted Visual Basic region names are matched without their quotes, and region markers declared as JSON keys are recognized as an extension, plain JSON having no comments to put a marker in. Co-authored-by: Miroma <its.miroma@proton.me> Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2 months ago