chore(devDeps): upgrade eslint packages #1103
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #1103 +/- ##
=======================================
Coverage 75.52% 75.52%
=======================================
Files 80 80
Lines 16153 16153
Branches 1520 1520
=======================================
Hits 12200 12200
Misses 3914 3914
Partials 39 39
☔ View full report in Codecov by Sentry. |
JKRhb
force-pushed
the
eslint-update
branch
from
f55bf32 to
195c82b
Compare
JKRhb
requested review from
danielpeintner,
egekorkan,
relu91 and
sebastiankb
as code owners
relu91
approved these changes
Oct 2, 2023
Member
relu91
left a comment
relu91
left a comment
There was a problem hiding this comment.
Thanks this was very well needed.
danielpeintner
approved these changes
Oct 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the context of #1097, I noticed that eslint currently reports a couple of false positives when it comes to typing. Furthermore, when running
npm run lint, it warns of missing compatibility with the currently used TypeScript version.This PR simply updates all of the eslint-related packages and applies some (partially automated) fixes to the codebase.