View Source unused_configuration_options (rebar3_hank v1.4.1)
To avoid this warning, remove the unused parameters.
note
Note
For this rule to apply, it's assumed that configuration options for an Erlang application are only consumed within said Erlang application or the other applications in the same umbrella project. If you have a dependency that consumes an environment parameter from one of your project applications, you can add an ignore rule in rebar.config for it.
Link to this section Summary
Functions
Detects unused config options. It gets the options from .config and .app.src files and then:
- Builds an index with file/options.
- Gets the atoms used around the .erl and .hrl files.
- Calculates the unused atoms (options) and return the results.
Rule ignore specifications. Only valid in rebar.config since attributes are not allowed in config files. Example:
{hank, [{ignore, [
{"this_file.config", unused_configuration_options, [ignore_option]}
]}]}.
Link to this section Functions
-spec analyze(hank_rule:asts(), hank_context:t()) -> [hank_rule:result()].
- Builds an index with file/options.
- Gets the atoms used around the .erl and .hrl files.
- Calculates the unused atoms (options) and return the results.
-spec ignored(hank_rule:ignore_pattern(), term()) -> boolean().
{hank, [{ignore, [
{"this_file.config", unused_configuration_options, [ignore_option]}
]}]}.