[Fix #448] Auto-correct multi-line parameters in AlignParameters.
Merge pull request #506 from jonas054/fix_align_param

[Fix #448] Auto-correct multi-line parameters in AlignParameters.
Replace MethodAndVariableSnakeCase with MethodAndVariableNaming.

Add config parameter EnforcedStyle, with values snake_case and camelCase.
Merge pull request #507 from jonas054/method_and_variable_naming

Replace MethodAndVariableSnakeCase with MethodAndVariableNaming.
Fix a copy-paste error that put a comment in the wrong place.
Merge pull request #508 from jonas054/fix_comment

Fix a copy-paste error that put a comment in the wrong place.
Transfer responsibility of offence format and color to formatters

Also made severity coloring logic DRY.
Remove duplicated #report_summary specs

ClangStyleFormatter just uses inherited #report_summary.
Add Offence#corrected?
Print [Corrected] if the offence is auto-corrected in some formatters

This affects to simple/clang/progress/emacs formatters.
Add `corrected` value to offence objects in JSON formatter
Print correction count in final summary if corrected any offences

This affects to simple/clang/progress formatters.
Merge pull request #509 from yujinakayama/indicate-autocorrection

Indicate corrected offences in formatters
Support disabling Syntax offences with warning severity

This allows to disable only warning offences.
fatal/error offences (i.e. invalid syntax) cannot be disabled since
suppressing them does not make sense.

This fixes #493.
Merge pull request #510 from yujinakayama/support-disabling-syntax-offences

Support disabling Syntax offences with warning severity
Fix bug concerning different RunRailsCops in different directories.

Before this fix, the value of RunRailsCops for the first inspected file would be used for all files.
Merge pull request #511 from jonas054/fix_mobilized_cop_classes_bug

Fix bug concerning different RunRailsCops in different directories.
[Fix #512] Fix bug causing crash in AndOr auto-correction.

When checking if auto-correction changes the grammatical meaning of the node, we used the original node whose ranges refer to the whole file. Must use the new node we get from parsing the and/or expression.
Merge pull request #513 from jonas054/fix_and_or_crash

[Fix #512] Fix bug causing crash in AndOr auto-correction.
Extract method Util.source_length