rebar3 dialyzer

[phani35]

Does rebar3 dialyzer do analysis on all erlang applications under _build/default/lib ?.
I get more warnings when I run dialyzer -r _build/default/lib --plt _build/default/rebar3_24_plt.

Thanks,
Phani

[ferd]

It does not by default. See https://rebar3.org/docs/configuration/configuration/#dialyzer :

{dialyzer, [{warnings, [warning()]},
            {get_warnings, boolean()},
            {plt_apps, top_level_deps | all_deps} % default: top_level_deps
            {plt_extra_apps, [atom()]},
            {plt_location, local | file:filename()},
            {plt_prefix, string()},
            {base_plt_apps, [atom(), ...]},
            {base_plt_location, global | file:filename()},
            {base_plt_prefix, string()}]}.

If you configure Dialyzer with {dialyzer, [{plt_apps, all_deps}]}. it will run on all applications under the build directory.

[phani35]

Yes I have added all_deps option. Still observe there is a difference. I get more warnings when I run legacy dialyzer.

{dialyzer, [ {warnings, [unknown]}, {plt_apps, all_deps} ]}.

[ferd]

oh yeah, the unknown warnings were dropped by default, I think we wanted to bring them back but were caught by backwards compat issues since that would blow up people's builds. The default set of option varies between rebar3 and bare dialyzer, but that set can be configured to be equivalent.

[phani35]

In my case it is not scanning the dependencies under _build/default/lib.
one more question, is it possible to include _build/default/checkouts folder as well to run rebar3 dialyzer.

Thank you.

[ferd]

The checkouts directories get the apps handled as a top-level app, so they should generally be included. The files are however located elsewhere in the _build directory.