Inconsistent option name: max vs. maximum

The new max-statements-per-line has max option, but other existing rules (including max-statements) have maximum.

• http://eslint.org/docs/rules/max-statements
• http://eslint.org/docs/rules/max-depth
• http://eslint.org/docs/rules/max-nested-callbacks
• http://eslint.org/docs/rules/complexity
• http://eslint.org/docs/rules/max-params

Is this intentional?

[nzakas]

Yeah, we should fix this for sure. Assuming we stick with max everywhere, that would mean that we’d need to:

1. Ensure rules that accept maximum also accept max (update the rule schema so it accepts both).
2. Change the rule docs to use max while adding a note that the option name maximum is deprecated and will be remove at some point in the future.

[ilyavolodin]

So 3 with max and 5 with maximum. Even though maximum appears in more places, I would rather have max as the default. Max is self-explanatory and less typing.