-
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
Dev containers do not have built-in plugins #14137
Comments
Thanks for the fast reply. I replicated it with Theia IDE 1.53.100 as well(also updated the ticket). I will take a detailed look at the PR you linked in a minute, but would you expect this to work automatically with any product or are there some requirements on the products side to configure this/install the plugins in a certain way? |
It might be that the |
@sgraband Could you provide us with some more information on how your plugins setup is? Do you set the --plugins option or the THEIA_DEFAULT_PLUGINS env variable? Are you installing some plugins manually before connecting with the container? Is it a pacakges electron distribution with an asar file? |
@jonah-iden FYI I believe this is simply reproducible with the Theia IDE available from our website. No additional options necessary. |
@msujew ok thanks will try it out |
@jonah-iden. Yes i was reporting this straight from the Theia IDE. Thanks for looking into it. |
Bug Description:
Currently dev containers are started without the built-in plugins of the "parent" application (e.g. Theia IDE).
This leads to the application behaving differently than outside of the dev container, for example the syntax highlighting is missing.
I do not think, that the creator of the
devcontainer.json
file should be responsible for specifying the built-in plugins, as one would expect that they are "part of the application".Steps to Reproduce:
Additional Information
The text was updated successfully, but these errors were encountered: