Conversation
|
Note the |
ssbarnea
left a comment
There was a problem hiding this comment.
You missed the most important bit: adding eslint to .pre-commit-config.yaml so it runs during linting.
If you do this you do not need to alter any github actions.
BeyondEvil
left a comment
There was a problem hiding this comment.
Almost every var can be changed to const.
Add this rule: https://eslint.org/docs/rules/prefer-const
And it should help you out.
Let me take some time today and read over the rule list to see what else we may want to add |
Good point @ssbarnea, thank you for pointing this out. I've updated the PR accordingly |
|
@BeyondEvil @ssbarnea I've gone through the rule list and added every rule I thought made sense that didn't involve sweeping changes ( I'd feel safer adding those in a follow up PR to avoid breaking things ) except for the following sections: From the rest of the rule list, I intentionally skipped the following rules since they involved making a refactor, which I want to address in a follow up PR to decrease the size of this one:
If we are happy with this PR, I'd like to raise the above as separate issues after this merges so we don't forget about them and add them in time permitting. |
BeyondEvil
left a comment
There was a problem hiding this comment.
LGTM! 🎉
But let's wait for @ssbarnea before merging.
Add ESLint for JS linting.
This better sets us up to tackle #350, and should be added in as a best practice regardless.
The
.eslintrc.jsonfile was auto-generated byESLint.