Repository navigation
feat: concise line starts: ignore ;, read [ and - names, and name tags ended before a name - #261
Conversation
🦋 Changeset detectedLatest commit: 32715b5 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #261 +/- ##
=======================================
Coverage 99.89% 99.89%
=======================================
Files 35 35
Lines 4711 4753 +42
Branches 912 920 +8
=======================================
+ Hits 4706 4748 +42
Misses 4 4
Partials 1 1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
;, read [ and - names, and name tags ended before a name
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 32 minutes. View limit details
No actionable comments were generated in the recent review.
|
b40efd0 to
23693db
Compare
…me tags ended before a name - An open tag that ends before its name (eg a line of just `,`, or `<,>`) is named empty, so a tag never ends without `onOpenTagName`. - A concise line starting with `;` is ignored; only comments may follow. - A concise line starting with `[` reads the group after an empty name. - A concise line starting with `-` and a word character (eg `-if`) opens a tag whose name starts with `-`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
23693db to
32715b5
Compare
Fixes and additions for what a concise line can start with:
,(eg while typing) or<,>. The parser then emittedonOpenTagEndwithoutonOpenTagName, which crashed the Marko compiler and the language tools' parser (failing the whole TypeScript content mapper transform for the template), and<,>crashed the parser itself. Such a tag is now named empty where its open tag ends, as one starting with|,.or#already is.;is now ignored rather than opening a nameless tag. As after a tag's;, only comments may follow it.[reads the attribute group after an empty name, rather than reading the group's first attribute as the tag name ([a=1]was anatag with an attribute named "").-and a word character (eg-if) opens a tag whose name starts with-, as<-if>already does in HTML mode, for an upcoming feature.- textand a-line within a text-only tag are still errors.Input that already parsed correctly emits the same events as before. After release, the htmljs-parser floor in the compiler and prettier-plugin-marko should be raised.
🤖 Generated with Claude Code