-
Notifications
You must be signed in to change notification settings - Fork 211
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
Re-Enable ESLlint rules #11691
Comments
➕ 1️⃣ for enabling |
That is correct! |
Is it necessary for ALL of these rules to be re-enabled in one go? Or can we break this up into smaller chunks? I'm happy to lend a hand if you need help with this. I'm particularly missing |
Well, I usually take 1 at the time. In addition, I have to group the errors by code owners and create multiple PRs for each code owner per rule.
Yeah, absolutely! cc: @meganhkelley |
As an update, I'm working on fixing the issues around |
@bkjohnson would it be possible to set the |
We're unlikely to enforce that kind of behavior any time soon. If specific app teams want to adopt that style among themselves, then that's fine. |
I'm going to start chipping away at this one |
Working on the jsx/a11y linting rules first. Initial run turned up 231 errors. I'm fixing small ones and reaching out to teams for big issues that require more context to fix. Will likely turn these on as warnings until they're cleared out. |
I don't know if the issues are distributed conveniently enough for this to work without a lot of tedious effort, but we could use overrides to selectively turn those warnings into errors for certain directories. This could prevent them from popping up anywhere where they didn't already exist. |
Opened up a PR that should only turn on jsx-a11y linting error on changed files, so if someone is in there making changes they'll have to also fix the issues: department-of-veterans-affairs/vets-website#20034 We can use this as a mechanism for the rest as well moving forward |
To be able to upgrade ESLint to v. 7, some rules needed to be diasbled to complete the upgrade.
These rules need to be enabled again:
The text was updated successfully, but these errors were encountered: