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
We get pretty good syntax highlighting with our syn-rsx-based view macro in Leptos. Here's an example from VS Code:
The only issue is that closing tags are simply highlighted as plain identifiers, so a PascalCase component name looks like a struct, and a lowercased HTML element looks like a variable. I can imagine some ways I could improve this, but they rely on having access to the span of the closing tag. Unless I'm mistaken, the NodeName you can get from NodeElement::name() gives you the opening span, but there's not a way to get the span of the closing tag, if it exists.
The text was updated successfully, but these errors were encountered:
We get pretty good syntax highlighting with our
![Screenshot 2023-04-05 at 8 53 05 AM](https://user-images.githubusercontent.com/286622/230086133-f1a08286-e435-4b16-9ec5-12ee5e78387a.png)
syn-rsx
-basedview
macro in Leptos. Here's an example from VS Code:The only issue is that closing tags are simply highlighted as plain identifiers, so a PascalCase component name looks like a struct, and a lowercased HTML element looks like a variable. I can imagine some ways I could improve this, but they rely on having access to the span of the closing tag. Unless I'm mistaken, the
NodeName
you can get fromNodeElement::name()
gives you the opening span, but there's not a way to get the span of the closing tag, if it exists.The text was updated successfully, but these errors were encountered: