Prettify VSCode SDK output
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8.1k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
- I'd be willing to implement this feature (contributing guide)
- This feature is important to have in this repository; a contrib plugin wouldn't do
Describe the user story
When a user runs yarn dlx @yarnpkg/sdks vscode, changes are made to .vscode/extensions.json and .vscode/settings.json. When the user has configured Prettier to use tabs and manually edited the file beforehand, the files created by Yarn show up in git as changed every for line (apart from { and }).
Describe the solution you'd like
Check if Prettier is installed/enabled for JSON/not ignored for the files in question, and if applicable, run prettier on the generated output.
Describe the drawbacks of your solution
This section is important not only to identify future issues, but also for us to see whether
you thought through your request. When filling it, ask yourself what are the problems we could
have maintaining what you propose. How often will it break?
Describe alternatives you've considered
- Negligible impact on the duration of the
yarn dlx @yarnpkg/sdks vscodecommand
Thank you!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the yarn dlx @yarnpkg/sdks vscode entry point and inspect how it writes .vscode/extensions.json and .vscode/settings.json. Check the applicable Prettier configuration, then run the command against files using tabs; done means generated JSON respects enabled Prettier settings without changing unrelated content.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100