Skip to content

Releases: nishkohli96/eslint-config

Less code-style errors, More productivity!

31 Jan 07:36
a7283c3
Compare
Choose a tag to compare

"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

28 Jan 17:00
f0eecf8
Compare
Choose a tag to compare

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