Svelte grammar rejects legal text ampersands, greater-than signs and Svelte 5 attachments #429
Labels
No labels
code-review
correctness
dos
performance
security
severity/high
severity/low
severity/medium
tech-debt
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
h-dv/code-index#429
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A1X E4 on core 0.41.14 (
ea08d164), de.h-dv.svelte 0.2.0 reports five partial sources after embedded dispatch recovery. Independently reproduced all three minimal files with the published signed package and published 0.41.14 CLI/worker via isolatedplugin check --repo(no partner database changes):Each reports
extract.parse_error. The pinned tree-sitter-svelte-ng 1.0.2 grammar excludes both & and > from its text rule and has no attach production. E4 located these in CalendarImportButton/IcalEventsPreviewTable/Components, ContextMenu, and BaseDataGridBody respectively. No diagnostic message/span is currently recorded, only the code.Fix grammar at its owned source/reproducible build boundary, regenerate kind IDs and extractor together, bump the immutable package version and preserve genuine malformed-input diagnostics. Add package-CI fixture assertions for each trigger, existing template/script boundaries and narrow attachment reference semantics; do not suppress parse errors in the host. Related #279 is the broader testing gap, not this specific syntax defect.
Released in Svelte 0.2.1, with core 0.41.15. The published binary passed signed runtime acceptance for legal text ampersands/greater-than signs, attachments and attachment-to-TypeScript binding across restart. An upgrade using the actual official signed 0.2.0→0.2.1 packages reproduced the old parse error and cleared it without deleting the existing database; its inode was preserved. The actual package and channel were independently admitted with compiled trust anchors. Final release CI is green. Separate resolution gaps #433 and #434 remain open.
Partner confirmation after upgrading to core 0.41.15 (
065c8864), Svelte 0.2.1 and C# 0.1.7: all five previously failing Svelte components now extract successfully, Svelte refusals are zero, and the existing database was kept. Reported partial sources fell from six to one; the remaining one is a known malformed dataset fixture, outside Svelte. Historical parse-error contribution rows remain only in retired generations markeddeleting, not the live projection. This confirms the syntax repair on a real partner project as well as the release fixtures. The separate Svelte resolution issues #433/#434 remain open.