Fix leftover linting errors #45
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
…y interested in its side effect. also silences the linter error assosciated with it
|
Intentionally voiding accessor property expressions in tests as we are only interested in the side effects of the getter and the returned value is discarded. |
…n[]) => unknown. This silences no-unsafe-function-type linting rule and restores minimal type-safety (no implicit any) while leaving runtime behaviour untouched.
|
Replaced the blanket |
tegefaulkes
reviewed
May 16, 2025
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.
Description
This is a simple PR which fixes leftover linting errors discovered by the new js-lint package.
Issues Fixed
Tasks
Final checklist