v2.0.3 - Update Docs to prepare for release (#12)

Major upgrade

1. Migrate this project to a monorepo
2. Official Docs 📖 for the config 🎉
3. eslint-flat-config package compatible with eslint 9 and above
4. Modify 3 , disable 1 and remove 7 rules
5. Add more test codes in __tests__ folder

v2.0.2 - Fix keyword-spacing and comma-dangle

Released - 12 Apr, 2024

Modify space-before-blocks and comma-dangle config.

Set keyword-spacing in space-before-blocks rule to keywords: 'always'. Previous config was resulting in no spacing something like,

if(){}
catch{ 

Remove comma dangle from arrays and objects, as traling commas were creating readability issues, in sequelize queries.

Bug fixes

• Add the following rules in js config
  • @typescript-eslint/no-explicit-any
  • array-element-newline
  • newline-per-chained-call
  • space-before-blocks
  • space-infix-ops
• Modify comma-dangle config.

Split JS and JSX Rules

Released - 10 Apr, 2024

• Split js and react-jsx rules
• Turn off @typescript-eslint/ban-ts-comment
• Upgraded @stylistic/eslint-plugin, @typescript-eslint/eslint-plugin, @typescript-eslint/parser and eslint-plugin-react dependencies.

Upgrade Dependencies, remove es2024 & no-mixed-spaces-and-tabs rule

• Upgraded @stylistic/eslint-plugin, @typescript-eslint/eslint-plugin and @typescript-eslint/parser dependencies.
• Removed es2024 key from env.
• Turn off no-mixed-spaces-and-tabs rule.

Less code-style errors, More productivity!

"More developer friendly, Yay! 😃"

Approx 90% of the rules used now warn instead of throwing an error, so you can focus more on writing the logic, and not on formatting the code! Only the rules that throw an error and some exceptional warn rules like 'no-debugger' must be fixed by the developer.

Also, added some cool new badges in README.md thanks to Shields.io!

v1.0.2

While using this package during my development, I felt that the status of the rules listed below needed to be changed from error to warn as they would cause my app to crash, prompting me to alter my code to keep eslint happy (and make me irritated instead 😡). These rules would automatically fix the code on running the yarn lint script.

These rules are listed below -

Rule Name
comma-dangle
ban-ts-comment
eol-last
jsx-one-expression-per-line

The below rule is removed from the config file.

Rule Name	Reason
multiline-comment-style	the default setting starred-block read commented code as a comment itself, which made it difficult to uncomment the code