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

Add support for a configuration file #60

Open
axelson opened this issue Sep 22, 2019 · 1 comment · May be fixed by #338
Open

Add support for a configuration file #60

axelson opened this issue Sep 22, 2019 · 1 comment · May be fixed by #338
Labels
enhancement New feature or request work in progress

Comments

@axelson
Copy link
Member

axelson commented Sep 22, 2019

This is in addition to the workspace/didChangeConfiguration option.

Could look at erlang-ls/erlang_ls#61 for inspiration

@znorris
Copy link
Sponsor Contributor

znorris commented Apr 6, 2023

I've run into a case where I believe adding support for a configuration file would prove helpful.

I recently resolved an issue where :yamerl was incorrectly throwing an error while I was debugging my application. The fix was adding an excludedModules key to the Elixir LS configuration. (Thanks for having the note about NIFs in the README)

"excludeModules": [
    ":yamerl"
]

Being able to exclude this any time the project is running Elixir LS would be very helpful as it will give a deliberate place to share this knowledge among other developers.

I'm using the VS Code extension which allows me to save the exclusion in our repo via the .vscode/launch.json file. However, the exclusion has to be duplicated among VS Code launch configurations, and obviously it won't be available to non VS Code devs.

Thanks for what you do! 🥳

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request work in progress
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants