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

Fix VS Code settings and its lints #37640

Closed
wants to merge 1 commit into from
Closed

Conversation

manzoorwanijk
Copy link
Member

There are lints in .vscode/settings.json and I don't know how but those lints are fixed everytime I run pnpm install or switch branches and I have to discard it everytime and it's annoying.

Proposed changes:

  • Fix lints in VS Code settings

Other information:

  • Have you written new tests for your changes, if applicable?
  • Have you checked the E2E test CI results, and verified that your changes do not break them?
  • Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

Does this pull request change what data or activity we track or use?

Testing instructions:

  • Just check that ESLint etc. fixes the lints in VS Code

@manzoorwanijk manzoorwanijk added the [Status] Needs Review To request a review from fellow Jetpack developers. Label will be renamed soon. label May 30, 2024
@manzoorwanijk manzoorwanijk requested a review from a team May 30, 2024 09:22
@manzoorwanijk manzoorwanijk self-assigned this May 30, 2024
Copy link
Contributor

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

  • ✅ Include a description of your PR changes.
  • ✅ Add a "[Status]" label (In Progress, Needs Team Review, ...).
  • ✅ Add testing instructions.
  • ✅ Specify whether this PR includes any changes to data or privacy.
  • ✅ Add changelog entries to affected projects

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.
Then, add the "[Status] Needs Team Review" label and ask someone from your team review the code. Once reviewed, it can then be merged.
If you need an extra review from someone familiar with the codebase, you can update the labels from "[Status] Needs Team Review" to "[Status] Needs Review", and in that case Jetpack Approvers will do a final review of your PR.

@manzoorwanijk manzoorwanijk enabled auto-merge (squash) May 30, 2024 09:46
Comment on lines 2 to 4
"editor.codeActionsOnSave": {
"source.fixAll.eslint": true,
"source.fixAll.eslint": "always"
},
Copy link
Contributor

@anomiex anomiex May 30, 2024

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. 😀

Copy link
Contributor

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.

@tbradsha tbradsha mentioned this pull request Jun 12, 2024
3 tasks
@manzoorwanijk
Copy link
Member Author

Closing in favour of #37498

auto-merge was automatically disabled June 13, 2024 10:55

Pull request was closed

@manzoorwanijk manzoorwanijk deleted the fix/vs-code-settings branch June 13, 2024 10:55
@github-actions github-actions bot removed the [Status] Needs Review To request a review from fellow Jetpack developers. Label will be renamed soon. label Jun 13, 2024
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