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

HTML indention does not work correctly in eex and leex files #162

Closed
2 tasks done
bdtomlin opened this issue Jan 21, 2021 · 2 comments
Closed
2 tasks done

HTML indention does not work correctly in eex and leex files #162

bdtomlin opened this issue Jan 21, 2021 · 2 comments

Comments

@bdtomlin
Copy link

bdtomlin commented Jan 21, 2021

Is this the right repo? I think so.

Environment

Most of this can be filled out by running the VSCode command (by default bound to Ctrl+Shift+P) "ElixirLS: Copy Debug Info"

  • Elixir & Erlang versions (elixir --version): Erlang/OTP 23, Elixir 1.11.3
  • VSCode ElixirLS version: v0.6.2
  • Operating System Version: macOS Big Sur 11.1

Troubleshooting

  • Restart your editor (which will restart ElixirLS) sometimes fixes issues
  • Stop your editor, remove the entire .elixir_ls directory, then restart your editor

HTML indenting doesn't work correctly in html.eex and html.leex files.

In an html.eex file using emmet if you type div you will end up with <div>|</div> where | is the cursor. If you hit enter you end up with the following where | is the cursor:

<div>
|</div>

If you change the file format to html and perform the same actions you get the following, which is also expected in the first example:

<div>
  |
</div>

Basically, the file is not utilizing html indention. FWIW, erb files have the same problem. PHP files work correctly so it is possible. I don't know anything about VSCode extensions, but I will try to dig in and figure out what the issue is at some point if no one else knows what is going on.

@axelson
Copy link
Member

axelson commented Jan 22, 2021

This is a subset of #98 which has some links to additional information if you'd like to dive in. Unfortunately microsoft/vscode#1751 still hasn't been implemented which would make this type of support much easier.

@lukaszsamson
Copy link
Collaborator

Fixed in #258

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

No branches or pull requests

3 participants