-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Run separate instance of Theia server with plugin that is developing #9212
Comments
workflow is when developping a theia plugin new theia plugin model (not an extension) ? |
Yes, this issue is only for new Theia plugin model. |
Small clarification about implementation. This is supposed to work with new plugin model, as was said above. Because new plugin model is an extension (not plugin) of Theia we have to do this issue on the same level, i.e. extension. Theia supports both browser and electron versions, so we have to do the same here. |
Hello, plugin is new isolated model, extension is the inversify extension (current theia extension model) |
This issue is a part of new plugin model implementation. It handles new plugins, but has to be implemented as current theia extension and contributed in Theia core (because we support running Theia without Che) |
I'm not sure to see why we're forced to use extension model instead of plugin model. |
That's what I wanted to say there:
|
In general yes, but when we work on plugin model (this issue as a part of the epic):
|
I think there is something missing between this issue and the plugin model implementation. This issue is about running another theia with plugins that are in development the workspace to be tested in the browser:
if you are working on the plugin model implementation you should create a subtask or link to the related issue. |
Done for Theia without Che. |
When user develops Theia plugin in Che - there are should be an ability to configure and run separate instance of Theia with current plugin inside. For such development mode - a new “tab browser” with a new instance of Theia running should be opened.
The text was updated successfully, but these errors were encountered: