Address linter warnings [wip] - #8220
Closed
ksen0 wants to merge 1 commit into
Closed
Conversation
ksen0
marked this pull request as draft
October 31, 2025 09:25
ksen0
force-pushed
the
2.0-lint-warnings
branch
from
October 31, 2025 09:26
97fd81b to
c1b2fc1
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Linter warnings are surfaced in PRs, including some older ones. This PR fixes the historical warnings that show up (example), to reduce clutter.
WIP: after
% npm run lint -- --fix, 319 problems remain, mostly line length.npm run lintpasses