Eslint: run fix with new rules #29997
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
s-rigaud
force-pushed
the
run-eslint-fix
branch
from
b42c806 to
bbf1192
Compare
Mugen87
approved these changes
Nov 29, 2024
cmhhelgeson
pushed a commit
to cmhhelgeson/three.js
that referenced
this pull request
Dec 5, 2024
Co-authored-by: Samuel Rigaud <[email protected]>
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
As the eslint rules have been updated on another PR, I re-run
npm run lint-fixon the project and I manually updated some errors.