-
Notifications
You must be signed in to change notification settings - Fork 36
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
Make built-ins extension pack #25
Comments
But for example apps we should not use pack but concrete extensions that extenders could pick, i.e. in Theia repo we just should update links don't exchange with a pack, not everybody wants to use everything. |
@akosyakov I am ok with that - the example applications can be a showcase of individual extensions that one can pick, in a granular way. Are you ok with the applications in |
yes for theia-apps is fine I wonder since we published to Open VSX Registry already, it would be good to make a PR in theia repo to update links |
@vince-fugnitto Would you have time to update the built-ins used in the main repo's example applications, to use the public Open VSX registry instead of GH Releases? e.g. a random one: |
Closing in favor of: #40 |
As a follow-up to #20, I was thinking that it would probably be easy to make an extension pack that would contain the subset of built-ins that are know to work well.
It would be useful as a shortcut to install the built-ins in one step
The text was updated successfully, but these errors were encountered: