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

Support for .vscode/extensions.json #8982

Closed
Kreyren opened this issue Jan 22, 2021 · 4 comments · Fixed by #9043
Closed

Support for .vscode/extensions.json #8982

Kreyren opened this issue Jan 22, 2021 · 4 comments · Fixed by #9043
Assignees
Labels
enhancement issues that are enhancements to current functionality - nice to haves help wanted issues meant to be picked up, require help vscode issues related to VSCode compatibility

Comments

@Kreyren
Copy link

Kreyren commented Jan 22, 2021

Expecting theia on gitpod to prompt installation of these extensions on startup (like vscode does).

Example file:

{
    "recommendations": [
        "ms-azuretools.vscode-docker",
        "exiasr.hadolint",
        "timonwong.shellcheck",
        "coenraads.bracket-pair-colorizer-2",
        "markwylde.vscode-filesize",
        "oderwat.indent-rainbow",
        "stephen-riley.regexworkbench",
        "medo64.render-crlf",
        "gruntfuggly.todo-tree",
        "vscodevim.vim",
        "slenderman00.vsirc",
        "genuitecllc.codetogether",
        "streetsidesoftware.code-spell-checker",
        "aaron-bond.better-comments",
        "tamasfe.even-better-toml"
    ]
}
@Kreyren
Copy link
Author

Kreyren commented Jan 22, 2021

ah it does that already.. my fault!

@Kreyren Kreyren closed this as completed Jan 22, 2021
@Kreyren
Copy link
Author

Kreyren commented Jan 22, 2021

My fault again, that was vscode. Theia doesn't have this behavior.

@Kreyren Kreyren reopened this Jan 22, 2021
@vince-fugnitto vince-fugnitto added enhancement issues that are enhancements to current functionality - nice to haves help wanted issues meant to be picked up, require help vscode issues related to VSCode compatibility labels Jan 22, 2021
@colin-grant-work
Copy link
Contributor

colin-grant-work commented Jan 29, 2021

@vince-fugnitto, I think I can take this one. Do you think it should be its own package - pretty light, but that would parallel preferences, tasks, debug/launch - or should it be put in one of the plugin-related packages? It'll be connected with the plugin search view, in part (VSCode lets you search for @recommended to get recommended plugins), so that might be a logical place for it.

@vince-fugnitto
Copy link
Member

@colin-grant-work I have not thought too much about it yet, but perhaps vsx-registry would be sufficient as a location? In the end we would need to use the registry api to fetch these extensions by id.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement issues that are enhancements to current functionality - nice to haves help wanted issues meant to be picked up, require help vscode issues related to VSCode compatibility
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants