Skip to content
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

Update to ESLint 8.57.0 #7150

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

Conversation

pjonsson
Copy link
Contributor

What this PR does

Renames .eslintrc to .eslintrc.js and bumps ESLint to 8.57.0.

This PR will not pass before #7148 and #7149 are merged and this is rebased on top of that.

Test me

Verify that the three added no-unsafe-optional-chaining ignores are safe.

Checklist

  • There are unit tests to verify my changes are correct or unit tests aren't applicable (if so, write quick reason why unit tests don't exist)
  • I've updated relevant documentation in doc/.
  • I've updated CHANGES.md with what I changed.
  • I've provided instructions in the PR description on how to test this PR.

@pjonsson pjonsson force-pushed the update-eslint branch 2 times, most recently from 91744ef to 8b68797 Compare May 22, 2024 07:11
@pjonsson pjonsson force-pushed the update-eslint branch 2 times, most recently from 70990a7 to 71b1a79 Compare September 19, 2024 09:01
@pjonsson pjonsson mentioned this pull request Sep 19, 2024
4 tasks
@pjonsson
Copy link
Contributor Author

@ljowen @na9da I rebased this after #7272 landed, and since there are now 0 lint warnings, this might be a good time to land this PR?

@pjonsson
Copy link
Contributor Author

@na9da this PR doesn't make anything worse than it is currently, and doesn't affect the "terriajs binary" so it is low risk. I assume there isn't a policy against using a newer ESLint on the code base, so is there anything preventing this from getting merged?

@pjonsson
Copy link
Contributor Author

Just noticed they had renamed the recommended rules for the typescript-eslint plugin. Re-enabling the recommended rules makes this no longer pass, so marking this PR as draft for now, and will make separate PRs of the fixes.

To start with, this depends on #7323.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant