-
Notifications
You must be signed in to change notification settings - Fork 53
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
Format on save does not respect imported formatter configuration #67
Comments
Ah, looks like they've added a lot of configuration options to the format task since I added support for it to ElixirLS. Unfortunately, supporting those features right now will likely involve copy-and-pasting a lot of private functions from Elixir. I'm willing to do that, but I think I also will send a PR to try to export some of the configuration functionality from I'll likely get to this sometime next week. |
I added a new function to You'll need to be running the latest (pre-release) version of Elixir for it to work, though. You can install it with |
Thank you 👍 |
Just published a release with the fix. |
I would suggest to re-open this issue. We are seeing an non-reproducible problem upon saving. |
^ seconded, seems to ignore edit: or may possibly be ignoring |
It's definetely adding parenthesis randomly upon saving (sometimes yes, sometimes not). |
I'm also seeing this issue (on the latest version) |
@zachdaniel Issues should be filed on the new repo (https://github.com/elixir-lsp/elixir-ls/). Although this one sounds like a duplicate of elixir-lsp/elixir-ls#402 |
From @Rosetjau on March 16, 2018 13:58
When running the formatter from command line via
mix format
the formatter respects the configuration that is imported from dependencies. The same does not seem to apply to the "format on save" feature in Visual Studio Code.I have set up an example repository to reproduce this issue. Steps to reproduce:
mix format
from command line. Notice that the formatter exits without changing theschema.ex
file, because the.formatter.exs
file imports the configuration that is exported by Absintheschema.ex
file and save itschema.ex
file, even if the Absinthe formatter configuration declares those functions/macros as locals_without_parensCopied from original issue: JakeBecker/vscode-elixir-ls#58
The text was updated successfully, but these errors were encountered: