Skip to content

feat(toHighlight): add new utility#222

Draft
J-Sek wants to merge 4 commits intomasterfrom
feat/to-highlight
Draft

feat(toHighlight): add new utility#222
J-Sek wants to merge 4 commits intomasterfrom
feat/to-highlight

Conversation

@J-Sek
Copy link
Copy Markdown
Contributor

@J-Sek J-Sek commented Apr 29, 2026

new utility meant to replace VHighlight internal logic

Early draft, I have barely looked at the code

@J-Sek J-Sek self-assigned this Apr 29, 2026
@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new Bot commented Apr 29, 2026

Open in StackBlitz

commit: c738606

mergeRanges now sorts, merges, and drops invalid (zero-width or inverted)
ranges before chunking, applied to both the query and caller-supplied
matches paths so unsorted or overlapping input produces correct output.
Adds per-symbol @example JSDoc, the tree-shaking side-effects marker,
Architecture mermaid + Reactivity section in the docs page, README sync,
and tests covering unsorted, overlapping, zero-width, inverted, and
out-of-bounds ranges plus reactive query/matches and getter inputs.
ref('foo') for a string primitive violates PHILOSOPHY §4.1 — shallowRef
is the right primitive for booleans, numbers, strings. Examples are
the de facto template for downstream consumers, so the rule has to hold
there too. Codifies the convention in .claude/rules/docs.md so future
example authors see it without needing to read PHILOSOPHY first.
The shallowRef-in-examples rule belongs on master as a project-wide
docs convention, not bundled with the toHighlight feature work.
Re-landing on master separately.
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.

2 participants