Thanks that looks very useful!
axelson
Scenic Core Team
jeremyjh
I’ve published a release candidate to hex:
{:dialyxir, "~> 1.0.0-rc.0", only: [:dev], runtime: false}
We also made a minor API change from the preview, dialyzer.explain is a new top-level task that replaces --explain and --list.
9
jeremyjh
Hi, we are really close, but have had a few issues slowly trickling in. The plan is to push another RC tomorrow and a final 1.0.0 a week from tomorrow (July 6th).
3
sorentwo
Oban Core Team
My experience running the beta was pretty good. The only issues I ran into was related to integration with Vim (through Ale). It just isn’t configured to display the new warning format yet.
Nice work all around, excited for this improvement to our tooling.
1
NobbZ
Thats what I like about the Elixir-LS. It calls into dialyzer itself and annotates the code. I’m eagerly waiting for the LS to integrate dialyxirs pretty printer, as dialyzer tooltips in the LS are in erlang form…
2
jeremyjh
If Ale is running mix dialyzer and displaying errors in the editor, it needs to pass --format short most likely.
1
sorentwo
Oban Core Team
Are you using LS through Vim/NeoVim? Apparently Ale is adding LS support, but I haven’t taken the time to enable it yet.
Good to know. Is that a 1.0 only option or can it be passed currently? I’m sure they’ll want to maintain backward compatibility for dialyxir 0.5 as well.
0
NobbZ
jeremyjh
It’s a new option in 1.0. I could release a 0.5 update that ignores it for compatibility but I don’t think that would help them, because it doesn’t fix the installed base and people willing to upgrade should just move to 1.0 anyway.
1