Skip to content

fix: align reload tag offsets and incremental file order#54

Merged
FanaticPythoner merged 2 commits into
masterfrom
fix/issue-53-errors-in-tag-processing-during-a-full-scan
May 31, 2026
Merged

fix: align reload tag offsets and incremental file order#54
FanaticPythoner merged 2 commits into
masterfrom
fix/issue-53-errors-in-tag-processing-during-a-full-scan

Conversation

@FanaticPythoner

Copy link
Copy Markdown
Owner

Ripgrep byte offsets are converted to JavaScript string offsets before
custom-regex normalization so reload scans match editor scans for COBOL and SQL
prefix patterns.

Detection:

  • resolve ripgrep submatch byte positions against physical line text
  • use UTF-8 byte-to-string offset conversion for absolute and local offsets
  • cover issue Errors in tag processing during a full scan #53 COBOL, SQL, bracket, and Unicode prefix cases

Tree:

  • limit tag-order sorting to grouped root tag nodes
  • keep sibling file nodes sorted by path after incremental document replacement

Packaging:

  • add npm publish ignores for source, tests, workflow tooling, and artifacts
  • preserve bundled dist runtime while excluding source maps

Coverage:

Fixes #53

Ripgrep byte offsets are converted to JavaScript string offsets before
custom-regex normalization so reload scans match editor scans for COBOL and SQL
prefix patterns.

Detection:
- resolve ripgrep submatch byte positions against physical line text
- use UTF-8 byte-to-string offset conversion for absolute and local offsets
- cover issue #53 COBOL, SQL, bracket, and Unicode prefix cases

Tree:
- limit tag-order sorting to grouped root tag nodes
- keep sibling file nodes sorted by path after incremental document replacement

Packaging:
- add npm publish ignores for source, tests, workflow tooling, and artifacts
- preserve bundled dist runtime while excluding source maps

Coverage:
- add issue #53 regex matrix coverage for raw ripgrep payloads
- add tree behavior coverage for sorted sibling files after updates
- add issue #53 microbenchmark summary for scan-large-custom-regex

Fixes #53
Walk first-parent ancestry from candidate refs so the equivalence harness selects
the nearest commit that still exposes baseline regex entries after registry
centralization.

Report audit child-process exits and malformed stdout before JSON parsing, with
QUnit coverage for both failure paths.
@FanaticPythoner FanaticPythoner merged commit e0861e7 into master May 31, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Errors in tag processing during a full scan

1 participant