Expand ESLint with further rules

[andrewtavis]

trafficstars

Terms

• [X] I have searched open and closed feature requests
• [X] I agree to follow activist's Code of Conduct

Description

This issue is to discuss and add new ESLint rules and also to refactor the codebase as needed to make it compliant after the changes :)

Contribution

@Robert-Kovalcuk had some ideas of some rules that we should add. Let's discuss and we can check in with some others and go from there!

[andrewtavis]

CC @to-sta :)

[Robert-Kovalcuk]

Yes, I'll definitely have a look at that, out of the top of my mind I think, we should enforce multi-word components

[andrewtavis]

Thanks @Robert-Kovalcuk!

[to-sta]

@Robert-Kovalcuk good idea 💯.

[to-sta]

Checking for type any would be interesting. Maybe there is a rule for disallowing type any.

[andrewtavis]

CC @lucianmurmurache: this is the ESLint issue I was talking with you about. @Robert-Kovalcuk, @lucianmurmurache is adding things into the ESLint setup to expand a11y linting. Figured adding him into the discussion makes sense 😊

[andrewtavis]

Hey @Robert-Kovalcuk 👋 Checking in on this one as it definitely would be good to expand the rules again soon :) Let me know if you have time for a call soon!