"anycode-*" on VS Code Marketplace: explain they're all included in "anycode"
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- vscode
- Domain
- documentation
Research direction
Start with the README.md files in each anycode-* subfolder and compare their Marketplace pages. Document that each language extension is included or automatically installed with the main anycode extension, including the option to uninstall unused languages, then publish the updated information to the Marketplace.
Written by the indexing model from the issue text.
Description
-
https://marketplace.visualstudio.com/items?itemName=ms-vscode.anycode-rust --> Q & A --> "Ask a question" forwarded me here, and there's no other obvious discussion/forums place/link, so please don't close this Github issue just because you can.
-
Is/was anycode-rust a subset/specialization of anycode for Rust only? If so, is it possible to keep it up to date? (https://marketplace.visualstudio.com/items?itemName=ms-vscode.anycode-rust&ssr=false#version-history)
-
Otherwise, please make it/mark it obsolete/unmaintained on the Marketplace, and/or make it redirect (if possible) or liknk to anycode.
EDIT: I see, anycode installs or includes other anycode-* extensions.
Please document that or make it obvious on the Marketplace page for each of anycode-. Ideally with README.md in each anycode- subfolder/directory, and then push to the Marketplace, so it's obvious both on GitHub and on Marketplace. You could even use same README.md for all, just mentioning something like "This VS Code extension is included/automatically installed as a part of the main anycode extension. If you do not use this language, you can uninstall it afterwards."
- Dominant language
- JavaScript
- Stars
- 387
- Forks
- 47
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Contributor guide
No contributing guide indexed for this repository
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.
More from microsoft/vscode-anycode
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
microsoft/vscode-anycode#186 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoft/vscode-anycode#149 ·
-
Usage examples Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
microsoft/vscode-anycode#128 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoft/vscode-anycode#78 ·
-
feature-request
microsoft/vscode-anycode#77 · 2 comments · 1 assignee ·
All issues in microsoft/vscode-anycode
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
antfu-collective/icones#398 ·
-
ECmail.com Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
wesbos/burner-email-providers#554 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
radiantearth/stac-browser#1023 ·
-
HMR stops working Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
components-web-app/docs#92 ·