Merge branch 'no-init-lists' of https://github.com/bormilan/elvis_core …

…into no-init-lists

RULES.md

@@ -61,7 +61,7 @@ identified with `(since ...)` for convenience purposes.
 - [State Record and Type](doc_rules/elvis_style/state_record_and_type.md)
 - [Used Ignored Variable](doc_rules/elvis_style/used_ignored_variable.md)
 - [Variable Naming Convention](doc_rules/elvis_style/variable_naming_convention.md)
-- [Not Use List In Init Functions](doc_rules/elvis_style/no_init_lists.md)
+- [No Init Lists](doc_rules/elvis_style/no_init_lists.md)
 - [Prefer Unquoted Atoms](doc_rules/elvis_text_style/prefer_unquoted_atoms.md)
 
 ## `.gitignore` rules

doc_rules/elvis_style/no_init_lists.md

@@ -2,8 +2,7 @@
 
 Do not use a list as the parameter for the `init/1` callback when implementing `gen_*` behaviours. It's semantically clearer to use a tuple or a map. [More info](https://erlangforums.com/t/args-in-gen-init-1/3169/5)
 
-> Works on `.beam` file? Not really! (it consumes results Ok, but these might be unexpected, since
-the files are pre-processed)
+> Works on `.beam` files? Yes!
 
 ## Options
 

src/elvis_style.erl

@@ -34,7 +34,7 @@
 -hank([{unnecessary_function_arguments, [{no_init_lists, 3}]}]).
 
 -define(NO_INIT_LISTS_MSG,
-        "Don't use a list as a parameter in 'init' function at position ~p.").
+        "Do not use a list as the parameter for the 'init' callback at position ~p.").
 -define(INVALID_MACRO_NAME_REGEX_MSG,
         "The macro named ~p on line ~p does not respect the format "
         "defined by the regular expression '~p'.").