ESLint rule configuration feedback

[nowyDEV]

Hey, there was a major update to the config recently #10

Highlights:

• New rules for consistent naming, sorting, commenting style
• New rules that enhance TypeScript & fill it's gaps (they are gonna be the most useful and also painful to fix)
• New rules for Node.js servers
• New rules to reduce tech debt & force refactoring of a codebase (smaller files, smaller functions, reduced complexity)
• Support for TypeScript 4.9 and satisfies operator

Many rules have been added, I'm setting up this thread to discuss them,
If you have any feedback regarding a new config, please feel free to post it here.

Possible topics:

• proposing new rules that would be useful
• complaints about current rules (why we should disable them or change to warnings)
• feedback about lint speed performance

[matassp]

The new rules are nice 👍 .
Just one thing: I saw this rule in eslintrc.js "unicorn/switch-case-braces", but it seems that prettier is cleaning up the braces.

[nowyDEV]

Yep, it was misconfiguration when the rules was transitioned to warning, the value inside this config is correct.

[matassp]

Would be nice to extend naming-convention rule to support number type object literal properties:

[nowyDEV]

Numbers are now ignored, added in https://github.com/nordcloud/eslint-config-pat/releases/tag/v4.8.0