Closed
Description
Many ESLint and TSLint rules start with "no-" to indicate a preference against some behavior. Some behaviors are always bad (e.g. no-eval), but others eventually are requested to have a preference towards. Having "no-" starting the rule name then makes it weird to add an option to encourage the behavior. For example:
- [no-parameter-properties] Support enforcing the inverse #103: [
no-parameter-properties] Support enforcing the inverse - [no-type-alias] Support enforcing the inverse #142: [
no-type-alias]: Support enforcing the inverse
Having only some rules start with no- also makes them a little less discoverable. There are a few more characters to scan through, and alphabetical lists make a little less sense.
Since it's already a conversion to go from TSLint to ESLint, can there be a preference set for not starting rule names with "no-"? In the two cases above, it'd be better if they were parameter-properties and type-alias.