-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ~H support #193
Add ~H support #193
Conversation
This only gets us partially there since some of the new ~H syntax engine won't properly syntax highlight the HTML. @msaraiva might have some insights on what it would take to properly highlight and whether it would make sense to add here or as a separate plugin ala Surface |
It's probably a good idea to add a separate entry for Since they have different grammars, it might be harder to provide unified rules for both of them, especially in the tag attributes area. Depending on how the existing grammar for The dependent nodes like |
@chrismccord I can take a stab at it after finishing |
@axelson we're considering having a separate package for the Having the highlighter in a separate project makes it easier for us to maintain syntax changes and release them much faster, as well as avoiding adding more stuff to Do you think this is the way to go? Any downsides you can see besides forcing the user to install an extra package? |
I think that sounds good and I don't see any other downsides besides the extra package 👍 |
Sorry, for posting the question on a closed issue.
|
@xnkm8h a PR would be welcome |
@xnkm8h the plugin mentioned is: https://github.com/phoenixframework/vscode-phoenix And it does support Also I'm hoping that elixir-lang/tree-sitter-elixir#2 will make it easier to integrate |
The next Phoenix LiveView release supports a new ~H template engine, which deprecates ~L. I've updated the rules to support the new sigil. Thanks!