-
Notifications
You must be signed in to change notification settings - Fork 800
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
Fix VS Code settings and its lints #37640
Conversation
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖 The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available. Once your PR is ready for review, check one last time that all required checks appearing at the bottom of this PR are passing or skipped. |
"editor.codeActionsOnSave": { | ||
"source.fixAll.eslint": true, | ||
"source.fixAll.eslint": "always" | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I note this bit was probably accidentally added in #37418 (they also tried adding .vscode/settings.json
to .gitignore
, redundantly). Probably it should have been in the user's config instead, leaving this file to only specify exclusions and locations of linter programs.
But I'm going to punt on all this to @tbradsha who has strong opinions on this file. 😀
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
strong opinions on this file
Indeed, mostly centering around this PR's statement that "it's annoying"; I'll put up a post today soliciting more feedback. In the meantime, it's probably best to just remove the editor.codeActionsOnSave
section.
Closing in favour of #37498 |
Pull request was closed
There are lints in
.vscode/settings.json
and I don't know how but those lints are fixed everytime I runpnpm install
or switch branches and I have to discard it everytime and it's annoying.Proposed changes:
Other information:
Jetpack product discussion
Does this pull request change what data or activity we track or use?
Testing instructions: