Rules Removed
These rules were once included, but later removed in subsequent versions due to their inconsistency in certain scenarios after trying out in various node and react projects. You will need to manually add them in the rules of your .eslintrc, if needed.
| Rule Name | Reason |
|---|---|
| @stylistic/array-bracket-newline & @stylisticarray-element-newline | Sometimes smaller array elements with more than 4 items can be wrapped in one line, whereas 3 items with longer character length, like list of urls need to be wrapped in new line |
| @stylistic/comma-dangle | Personal preference to retain or remove comma in arrays, objects, function args, imports and exports |
| @stylistic/lines-around-comment | Sometimes reqd, when writing block comments above functions, but don't need when writing block comment between 2 lines of code |
| @stylistic/no-mixed-operators | gave err in a + b * c, assuming dev is sensible enough to add parens themselves when too many operators being used in a single line of code |
| @stylistic/object-property-newline | Inconsistent in formating object, making it hard to read |
| @stylistic/newline-per-chained-call | This rule with default chain length 2 resulted in awkward readability when chaining operations |
| @typescript-eslint/ban-ts-comment | A good developer will avoid writing ts-comments, except in extreme cases. Let's not cause them trouble to write one more line |
| @typescript-eslint/no-this-alias | Sometimes this is reqd in fn context. eg. MongooseSchema.pre() |
| arrow-body-style | Extra effort for developer if he needs to add some more code before returning from a function. |
| dot-notation | prop name doesnt exist, but I have still assigned value for it. Using obj?.['name'] would work but obj.name would throw ts err |
| id-denylist | Use if required. eg. "id-denylist": ["warn", "e", "cb", 'callback'] |
| id-length | Warning when using _ for unused vars |
| jsx-first-prop-new-line | |
| multiline-comment-style | The default setting starred-block read commented code as a comment itself, which made it difficult to uncomment the code |
| no-mixed-spaces-and-tabs | Same rule in eslint.style |
| no-shadow | Gave unwanted warnings when using enums |
| no-unused-vars | @typescript-eslint/no-unused-vars does it better |
| react/react-in-jsx-scope | React v17+ doesn't require import React from react |
| react/jsx-uses-vars | Causing issues with flat-config while importing react-plugin |
| sort-keys | Sometimes more crucial object keys should come first |
| sort-vars | Same as above |