Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Addons: Auto-fix linting problems #27457

Merged
merged 1 commit into from
Dec 27, 2023

Conversation

hybridherbst
Copy link
Contributor

Description

Running the automatic linting fix (npm run lint-addons -- --fix) brings 93 problems (60 errors, 33 warnings) down to 37 problems (4 errors, 33 warnings) and makes it a bit easier to adhere to the coding standards in new files and PRs.

This contribution is funded by Needle

Brings 93 problems (60 errors, 33 warnings) down to 37 problems (4 errors, 33 warnings).
@Mugen87 Mugen87 added this to the r161 milestone Dec 27, 2023
@Mugen87 Mugen87 merged commit cd614f6 into mrdoob:dev Dec 27, 2023
10 of 11 checks passed
@hybridherbst hybridherbst deleted the feature/auto-fix-linting branch December 27, 2023 22:38
hybridherbst added a commit to needle-tools/three.js that referenced this pull request Dec 27, 2023
Brings 93 problems (60 errors, 33 warnings) down to 37 problems (4 errors, 33 warnings).
hybridherbst added a commit to needle-tools/three.js that referenced this pull request Dec 27, 2023
Brings 93 problems (60 errors, 33 warnings) down to 37 problems (4 errors, 33 warnings).
hybridherbst added a commit to needle-tools/three.js that referenced this pull request Dec 27, 2023
Brings 93 problems (60 errors, 33 warnings) down to 37 problems (4 errors, 33 warnings).
AdaRoseCannon pushed a commit to AdaRoseCannon/three.js that referenced this pull request Jan 15, 2024
Brings 93 problems (60 errors, 33 warnings) down to 37 problems (4 errors, 33 warnings).
@LeviPesin
Copy link
Contributor

@mrdoob @Mugen87 Maybe we could actually enable checking addons lint in CI tests so that this could be detected on PRs level?

@hybridherbst
Copy link
Contributor Author

@LeviPesin I'd be very much in favor of that, but before it can be enabled there would be the above mentioned 37 errors and warnings to resolve, which I don't know how to resolve.

@LeviPesin
Copy link
Contributor

Hm... I can try to look into them after I'll file the nodes PRs I'm planning soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants