Skip to content
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

Support HEEx and Surface files #204

Merged
merged 1 commit into from
Aug 13, 2021
Merged

Conversation

msaraiva
Copy link
Collaborator

@msaraiva msaraiva commented Aug 12, 2021

This PR along with elixir-lsp/elixir-ls#583 adds support for HEEx and Surface templates. The changes allow VS Code to:

  1. Watch .heex and .sface files so recompilation is triggered when they change
  2. Activate the ElixirLS server when .heex or .sface files are open (otherwise the server is only initiated when you open an elixir file)
  3. Properly show error/warnings when originated in .heex or .sface files

@lukaszsamson I still have to make some changes in ElixirSense to improve the integration. Currently, suggestions/autocomplete are not aware of the template context so they are mostly considering the whole file as elixir code which brings a poor experience. I'll try to work on that next week.

Since the changes implemented in this PR have no dependency from any of the planned changes in ElixirSense, they can be applied independently.

@chrismccord this PR also closes #193 as the syntax highlighting was already implemented in https://github.com/phoenixframework/vscode-phoenix.

Copy link
Member

@axelson axelson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Thanks! ❤️

@axelson axelson merged commit dae2a8e into master Aug 13, 2021
@axelson axelson deleted the ms-support-heex-and-surface branch August 13, 2021 19:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants