-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Implement ExtensionMode
#10201
Labels
Comments
tsmaeder
added
plug-in system
issues related to the plug-in system
vscode
issues related to VSCode compatibility
labels
Sep 30, 2021
48 tasks
@eneufeld is looking into this issue. |
eneufeld
added a commit
to eclipsesource/theia
that referenced
this issue
Apr 1, 2022
The plugin context was hardcoded to have the production extensionMode. Now a flag is passed to mark a plugin as under development when deploying it. This flag is stored in the plugin metadata and later set in the plugin. When creating the context this flag is then converted to the correct extensionMode. Fix eclipse-theia#10201 Contributed on behalf of STMicroelectronics Signed-off-by: Eugen Neufeld <[email protected]>
eneufeld
added a commit
to eclipsesource/theia
that referenced
this issue
Apr 1, 2022
The plugin context was hardcoded to have the production extensionMode. Now a flag is passed to mark a plugin as under development when deploying it. This flag is stored in the plugin metadata and later set in the plugin. When creating the context this flag is then converted to the correct extensionMode. Fix eclipse-theia#10201 Contributed on behalf of STMicroelectronics Signed-off-by: Eugen Neufeld <[email protected]>
eneufeld
added a commit
to eclipsesource/theia
that referenced
this issue
Apr 1, 2022
The plugin context was hardcoded to have the production extensionMode. Now a flag is passed to mark a plugin as under development when deploying it. This flag is stored in the plugin metadata and later set in the plugin. When creating the context this flag is then converted to the correct extensionMode. Fix eclipse-theia#10201 Contributed on behalf of STMicroelectronics Signed-off-by: Eugen Neufeld <[email protected]>
1 task
eneufeld
added a commit
to eclipsesource/theia
that referenced
this issue
May 20, 2022
The plugin context was hardcoded to have the production extensionMode. Now a flag is passed to mark a plugin as under development when deploying it. This flag is stored in the plugin metadata and later set in the plugin. When creating the context this flag is then converted to the correct extensionMode. Fix eclipse-theia#10201 Contributed on behalf of STMicroelectronics Signed-off-by: Eugen Neufeld <[email protected]>
JonasHelming
pushed a commit
that referenced
this issue
May 25, 2022
* Add correct extension mode to plugin context The plugin context was hardcoded to have the production extensionMode. Now a flag is passed to mark a plugin as under development when deploying it. This flag is stored in the plugin metadata and later set in the plugin. When creating the context this flag is then converted to the correct extensionMode. Fix #10201 Contributed on behalf of STMicroelectronics Signed-off-by: Eugen Neufeld <[email protected]> * Remove passing `isUnderDevelopment` As indicated in a review, remove the passing `isUnderDevelopment` through the deployment system. * Rebase on master and include review comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Feature Description:
Add support for the
extensionMode
field in theExtensionContext
interface. We currently don't support running tests (as far as I know), but we should set "production" and "development" correctly when we run a hosted instance of Theia for a plugin under development.The text was updated successfully, but these errors were encountered: