axelson
Hi all! 
I’m pleased to announce that version 0.3.0 of the ElixirLS Fork project has been released! 
What’s new in 0.3.0
- Add workspaceSymbol support to quickly navigate to modules, functions, callbacks
- This is huge! Now you can navigate to a module by the module name, or navigate to a function with
f function_name, or a type witht type_name(full instructions are in the Readme) - VSCode use
Cmd+t(orCtrl+t), Spacemacs lsp-mode use, g s
- This is huge! Now you can navigate to a module by the module name, or navigate to a function with
- Elixir 1.10 support
- Provide completions for protocol functions
- Lots of ElixirSense fixes
- Various stability updates
Screenshot of workspaceSymbol support in action:
Full changelog: elixir-ls/CHANGELOG.md at v0.3.0 · elixir-lsp/elixir-ls · GitHub
Full diff: Comparing v0.2.28...v0.3.0 · elixir-lsp/elixir-ls · GitHub
Thanks to all the contributors that made this release possible:
- @lukaszsamson for the majority of the improvements (including the workspaceSymbol support)
- @cdegroot - Source asdf on startup
- Ahmed Hamdy - Updated startup message
- Jonáš Trantina - Requesting didSave in server capabilities
- @JakeBecker for the original implementation
If you’re using VSCode it should update automatically, if you’re running emacs lsp-mode or coc.vim you will probably have to update manually via git pull and then run mix elixir_ls.release again.
GitHub: GitHub - elixir-lsp/elixir-ls: A frontend-independent IDE "smartness" server for Elixir. Implements the "Language Server Protocol" standard and provides debugger support via the "Debug Adapter Protocol" · GitHub
VSCode: ElixirLS Fork: DEPRECATED (use original extension) - Visual Studio Marketplace
The reason for this fork
This fork started when Jake Becker’s repository became inactive for an extended period of time. So we decided to start an active fork to merge dormant PR’s and fix issues where possible. We also believe in an open and shared governance model to share the work instead of relying on one person to shoulder the whole burden.
Where Next?
Trending in Discussions
Other Trending Topics
Chat & Discussions>Discussions
Latest on Elixir Forum
Sponsor Spotlight
Build Elixir applications with speed and confidence.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Develop your skills with books, videos, and courses.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First 10 of 18 Posts
code-shoily
Thank you for the update. But it did not work for me for version Elixir 1.10, the autocomplete and jump to definition doesn’t work and there is a forever “Loading…” going on. I am using latest VS Code. Is there any step I need to follow to make it work with 1.10? Anyways, if it helps, I’ve attached the output Started ElixirLS Fork v0.3.0Elixir version: "1.10.0 (compiled with Erlang/OTP - Pastebin.com
It works great otherwise. Thanks again
mazz-seven
Woohoo a new version
Thank you for the hard work you put into it.
lukaszsamson
It seems that dialyzer PLT cache is out of date or corrupted. Please try removing .elixir_ls directory. As pointed out in the readme jump to workspace symbol currently requires dialyzer integration.
wolfiton
Thanks for the hard work @axelson.
maartenvanvliet
Thanks so much for the release!
alanvardy
Thank you @axelson, your efforts are much appreciated.
pedroassumpcao
Thanks @axelson! Incredible work.
code-shoily
Actually I tried removing that too. Didn’t work. But seems like I somehow had
vscode-elixirplugin enabled, and the moment I disabled it, it started working fine. And it goes without saying, amazing plugin, can’t thank the team enough for thisaxelson
Version 0.3.1 was released today!
General:
@speclines) is more reliableVSCode:
Full changelog
wolfiton
Thanks @axelson