Closed josefs closed 5 years ago
The configuration format is {dialyzer, [{exclude_mods, [gradualizer_prelude]}]}
, and not {dialyzer, [exclude_mods, ["gradualizer_prelude"]]}
as you entered it.
Note the tuples that act as a key/value pair. Changing the configuration to have the proper format should work.
Yes indeed. It would be helpful though if rebar gave a more informative error message.
Agreed. I think that's a general improvement that's a bit harder to drive as one single issue -- each provider (command) does its own handling. I'll close this issue, but we're welcoming of any contributions that can make such error handling clearer. Let me know if there's anything else that can be done in this issue and I'll reopen it.
Pre-Check
I'm happy to provide more feedback if needed in order to help resolve this question.
Environment
Current behaviour
We're using rebar for the Gradualizer project. I've encountered a situation where rebar crashes on us.
In order to reproduce, do the following:
The culprit seems to be that I've added the following line to
rebar.config
:{dialyzer, [exclude_mods, ["gradualizer_prelude"]]}.
Is there any way of achieving that without rebar crashing on me?
Expected behaviour
I expect rebar to run dialyzer as usual but pass the parameter
exclude_mods
with the value["gradualizer_prelude"]]
. I also expect rebar to no crash but exit normally.