Templates should only be in ~/.rebar3/templates and the built-in ones,
bar some specific overrides someone may want.
Looking recursively for templates in the CWD (.) may end up searching
nearly forever if the project is being created at the top of a very deep
directory tree, with extremely unlikely chances to find relevant
templates.
It causes more problems than benefits.
code:lib_dir/1,2 can return archive directory for rebar escript archive
applications, rather than the application's directory in the project.
Add dependencies not listed in `applications` to `dialyzer_plt_apps`.
Adds a base plt per OTP version that is stored in $HOME/.rebar3/. The
base plt is copied to new projects that don't have a plt for the active
OTP version. Modules are added/removed to the project's copy based on
the project's .app files.
Try to automatically detect all application dependencies when `plt_apps`
is not included in `rebar.config`.
Note that this will not follow `runtime_dependencies` in OTP
applications. This can be resolved by adding any missing
`runtime_dependencies` to `applications` in the .app.src file or
including `plt_apps` in `rebar.config`.
* Only include `plt_apps` (defaults to deps) in a single PLT
* Update PLT when `plt_apps` (or deps) are changed or updated
* Print warnings for all dialyzer runs (not just `succ_typings`)
The first variable can be unkeyed and the provider will sub in the
variable name 'name'. Additionally, the built-in templates and
documentation have been updated so that 'appid' is now 'name' and the
alternative commands are shown.