v3 - enforce no-explicit-any
#662
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
christinaroise
approved these changes
Sep 18, 2024
enabled eslint rule no-explicit-any and fixed reported errors
mathiazom
force-pushed
the
refactor/v3-no-explicit-any
branch
from
33935ef
to
a016ce0
Compare
mathiazom
force-pushed
the
refactor/v3-no-explicit-any
branch
from
a016ce0
to
6ac9fa4
Compare
anemne
approved these changes
Sep 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See #659
Enabled eslint rule
no-explicit-anyand fixed reported errorsChecklist
Please ensure that you’ve completed the following checkpoints before submitting your pull request: