chore: no-explicit-any #1248
Merged
chore: no-explicit-any #1248
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
Enable no-explicit-any linting rule and fix issues. Part of #1245. Signed-off-by: Tim deBoer <[email protected]>
deboer-tim
requested review from
dgolovin,
cdrage and
axel7083
and removed request for
a team
Fixes for svelte linting. Signed-off-by: Tim deBoer <[email protected]>
|
Ready for review. |
benoitf
approved these changes
Jan 30, 2025
|
note: please use branches in the forks rather pushing the branches to the original repository |
Sorry, didn't realize my git client had reverted target, will fix. |
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.
What does this PR do?
Enable no-explicit-any linting rule and fix issues.
Screenshot / video of UI
N/A
What issues does this PR fix or reference?
Part of #1245.
How to test this PR?
Code review, pr checks.