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
A Glimmer component name can have :: to denote a "namespace", where a component is inside of a directory
It might be nice to allow the namespace to be highlighted independently from the component name -- I'm sure there's a @namespace highlight or something, for languages like Ruby that use that frequently.
At the very least, the namespace should be part of the tag; : is not considered to be part of the tag right now.
<Directory::Component />
{{! <- namespace }}
The text was updated successfully, but these errors were encountered:
Not supporting this was reported in #2
Note that we use a short-cut here to enable mustache statements inside
of a string that disallows a `{` to appear inside a "concat statement".
Technically this should be allowed, though I would say it's quite rare.
Issue #3 was files to keep track of eventually fixing that, though it
will likely require moving the scanner into C to pull that off.
The problem is that `{` alone is safe, but `{{` together is not, and I'm
not sure you can write a regex that TreeSitter supports that can capture
that correctly.
I assumed that languages like Ruby, that use namespaced identifiers, highlight the namespace differently. It turns out that it doesn't seem like they do! Maybe we shouldn't, either... It might be enough to just highlight the :: separator itself as a single token.
A Glimmer component name can have
::
to denote a "namespace", where a component is inside of a directoryIt might be nice to allow the namespace to be highlighted independently from the component name -- I'm sure there's a
@namespace
highlight or something, for languages like Ruby that use that frequently.At the very least, the namespace should be part of the tag;
:
is not considered to be part of the tag right now.The text was updated successfully, but these errors were encountered: