-
-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clean up ESLint errors across the application #268
Comments
Thanks so much for submitting an issue! We have received it, will review it soon and follow up. |
I'll work on this! |
Hey @crisbnp, are you still working on this or is it up for grabs? If it's up for grabs I can start tackling some of them! |
Hey @seanwash ! I started working on this but currently working another open issue. Feel free to pick this up👍 |
🙌 Awesome! I'll self assign. |
hello @seanwash, are you working on this issue? Would love to give it a try in case you are not working on it. Thanks |
@Seremba go ahead! |
I've assigned it to you @Seremba. 😎 |
Goal
Now that we have the configuration being picked up thanks to #185, we can start fixing eslint issues. This is an all encompassing issues for eslint errors.
Reason
When you run eslint, there are a lot of errors
Tips
yarn eslint --fix pages/**/*.js
(swap pages for any other folder name to lint them instead: i.e.yarn eslint --fix components/**/*.js
to automatically fix any errors that eslint is capable of fixing. ESLint will also provide a list of remaining errors in the terminal.Definition of Done
The text was updated successfully, but these errors were encountered: