Rename rules and options

Looking at other plugins, they are tending to move away from no- and ignore prefixes.

Some of our rules names are also inconsistent, some end with statement while others don’t despite them both refering to statements.

New Name Proposals

Rules

Current Name	New Name	Theme
prefer-readonly-type		No mutability
no-let	enforce-const	No mutability
immutable-data		No mutability
no-method-signature	prefer-property-signature	No mutability
no-this-expression		No OO
no-class		No OO
no-mixed-type		No OO
prefer-type-literal		No OO
no-expression-statement		No statements
no-conditional-statement		No statements
no-loop-statement		No statements
no-return-void		No statements
no-throw-statement		No exceptions
no-try-statement		No exceptions
no-promise-reject		No exceptions
functional-parameters		Currying

Options

Current Name	New Name
ignoreAccessorPattern
ignoreLocal
ignoreClass
ignoreInterface
ignorePattern
allowMutableReturnType
ignoreImmediateMutation
allowArgumentsKeyword
allowNull
allowRestParameter
allowReturningBranches
allowUndefined
assumeTypes
checkImplicit
checkInterfaces
checkTypeLiterals
enforceParameterCount

---

Name Suggestion Are Most Welcome

[jonaskello]

When considering the rule names and separation, perhaps it would be help to identify some main themes that are needed to make typescript functional. Something like:

• Immutability
• No statements
• No exceptions
• No object orientation

[jonaskello]

@RebeccaStevens A big thank you for all the work you have put in to port the rules! 👍

Agreed #60 could be merged after release. I’ll go ahead and put the release candidate to use in some of the larger projects I’m working on as soon as I can to get a feel for the stability etc. Just need to migrate the projects from tslint to eslint first 😃