You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
If JS were altered to work like C, var test1 = a < b\nvar test2 = a > c (where \n represents an actual newline) could end up mishighlighted with <b var test2="a"> highlighted as an "element" of sorts that doesn't actually exist.
So I'm thinking a new {includeChild: 'scope'} pattern should exist. This would create a new "root" highlighting context for that subsection. This complements #83 (PR: #90) in that this feature isolates the matched grammar while that feature isolates the matched source. Most use cases would end up using both, so it might be worth merging the two, but I'm not sure if that's all use cases.
The text was updated successfully, but these errors were encountered:
Some grammars more or less "extend" grammars that let them:
$self
to recurse.But of course, with naïve inclusion, that causes problems.
var test1 = a < b\nvar test2 = a > c
(where\n
represents an actual newline) could end up mishighlighted with<b var test2="a">
highlighted as an "element" of sorts that doesn't actually exist.So I'm thinking a new
{includeChild: 'scope'}
pattern should exist. This would create a new "root" highlighting context for that subsection. This complements #83 (PR: #90) in that this feature isolates the matched grammar while that feature isolates the matched source. Most use cases would end up using both, so it might be worth merging the two, but I'm not sure if that's all use cases.The text was updated successfully, but these errors were encountered: