-
Notifications
You must be signed in to change notification settings - Fork 42
feat: add vscode-desktop-core
module
#278
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
base: main
Are you sure you want to change the base?
Conversation
# NOTE: There is a protocol whitelist for the token replacement, so this will only work with the protocols hardcoded in the front-end. | ||
# (https://github.com/coder/coder/blob/6ba4b5bbc95e2e528d7f5b1e31fffa200ae1a6db/site/src/modules/apps/apps.ts#L18) |
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.
👍🏼
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.
Thanks a lot @phorcys420. This will significantly enhance the DevEX for module development and maintenance.
> [!CAUTION] | ||
> We do not recommend using this module directly. Instead, please consider using one of our [Desktop IDE modules](https://registry.coder.com/modules?search=tag%3Aide). | ||
The VSCode Desktop Core module is a building block for modules that need to expose access to VSCode-based IDEs. It is intended primarily for internal use by Coder to create modules for VSCode-based IDEs. |
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.
The VSCode Desktop Core module is a building block for modules that need to expose access to VSCode-based IDEs. It is intended primarily for internal use by Coder to create modules for VSCode-based IDEs. | |
The VSCode Desktop Core module is a building block for modules that need to expose access to VSCode-based IDEs. It is intended primarily to be used as a library to create modules for VSCode-based IDEs. |
Let's make clear that anyone can use it to support any future VS Code-based IDE modules.
This PR introduces a new
vscode-desktop-core
module that acts similarly as AgentAPI does for other modules as an effort to centralize the logic.This will help with avoiding maintaining multiple modules that do the same thing. I will follow shortly with a PR for a
vscode-web-core
module to centralize the logic forvscode-web
andcode-server
as we've had issues where both would behave differently due to forgetting to update one or the other.This will also help make the amount of effort lower if we ever need to implement a module for another vendor (or if a community member does).
Modules update in #279