-
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
Open VSX Registry integration #6655
Conversation
packages/vscode-extensions/src/browser/vscode-extensions-service.ts
Outdated
Show resolved
Hide resolved
The items should have an 'install' button when not installed, and an 'uninstall' button when installed. |
The progress during installation should be shown with blue moving line above the search box, just as it does in other similar views. The button should turn to 'installing' during that. |
I cannot install any extension. The button spins forever. |
The search doesn't seem to work. If I search for 'Docker' I see many unrelated extensions. |
Regarding search: theia-ide/extension-registry#3 |
packages/vscode-extensions/src/browser/style/extension-detail.css
Outdated
Show resolved
Hide resolved
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.
Looked through the code:
- for the detail widget open handler should handle widget options properly and uri should be aligned with VS Code. We can test with webviews like Qarkus that clicking on java extension link opens the extension widget.
- generally I find naming of a package and types confusing, it should talk about registry, but looks like implementation of vscode extensions
- Also old code was copied without adjustment to our current code standards.
packages/vscode-extensions/src/browser/view/detail/vscode-extension-open-handler.ts
Outdated
Show resolved
Hide resolved
packages/vscode-extensions/src/browser/vscode-extensions-api.ts
Outdated
Show resolved
Hide resolved
packages/vscode-extensions/src/browser/vscode-extensions-api.ts
Outdated
Show resolved
Hide resolved
packages/vscode-extensions/src/browser/vscode-extensions-contribution.ts
Outdated
Show resolved
Hide resolved
packages/vscode-extensions/src/browser/vscode-extensions-service.ts
Outdated
Show resolved
Hide resolved
packages/vscode-extensions/src/browser/vscode-extensions-service.ts
Outdated
Show resolved
Hide resolved
96b5ac3
to
42a7f27
Compare
packages/vscode-extensions/src/browser/view/detail/vscode-extension-open-handler.ts
Outdated
Show resolved
Hide resolved
4752d5f
to
cea37e7
Compare
|
46143a8
to
b82a1c1
Compare
Please clean up the history: https://github.com/eclipse-theia/theia/blob/master/doc/pull-requests.md#checklist-commit-history There are many commits which fixes introduced by this PR. If it is hard then squash it. |
b82a1c1
to
d72e3bd
Compare
09a6474
to
36b5544
Compare
Signed-off-by: Anton Kosyakov <[email protected]>
Signed-off-by: Anton Kosyakov <[email protected]>
- Each plugin can be either of system or user type indicating that it was deployed by an embedding product or an end user. - System plugins are considered to be built built-in plugins. By default they are collected from `THEIA_DEFAULT_PLUGINS`, `THEIA_PLUGINS` variables or can be provided via `--plugins` cli option. - User plugins can are managed by an end user. They are stored either under user config plugins or extensions folder depending whether it is Theia plugin or VS Code extension. These plugins can survive the server restart. Signed-off-by: Anton Kosyakov <[email protected]>
…ode Marketplace Since it's violates MS TOS which allows only access only for products of the VS Code family. Theia based products has to provide own resolution. Signed-off-by: Anton Kosyakov <[email protected]>
Signed-off-by: Anton Kosyakov <[email protected]>
…and started Signed-off-by: Anton Kosyakov <[email protected]>
Signed-off-by: Anton Kosyakov <[email protected]>
36b5544
to
b7df3c1
Compare
I've rebased and addressed all comments from @vince-fugnitto and @spoenemann. @marcdumais-work @svenefftinge please have a look |
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.
I did another review pass and concluded with the following findings:
- verified that any new dependencies have approved licenses
- verified superficially the source code and could not identify any major issues
- verified that
builtin
extensions were correctly listed, and could not be removed
Past Issues:
- previous issues with icons (ex: gulp) has been successfully addressed
- the min height for the tree-view is successfully addressed
Issues:
- the search does not work properly (ex: search for 'a' yields not results but 'alt' does)
- when the progress bar is shown, there is a minor UI glitch where the rest of the view is pushed down
- an extension's readme should be displayed in the center, similarly to vscode (tested using
editorconfig
)
Improvements (now or in the future):
@vince-fugnitto I've filed an issue for the registry: eclipse/openvsx#34 cc @spoenemann I'm not sure about other issues, they seem to be minor. I would better invest time into integration tests for typescript againt new Monaco. Someone else can improve styling after this PR is merged. |
I'm going to merge it tomorrow if no objection. Theia 1.0 is already next week. |
👍
I'm fine with that, the improvements can be made iteratively at a later point. |
With the VSX (Extension) view now merged, is there still a reason to have the Plugins view? |
What it does
Widget where one can search and install VSCode Extensions from the Open VSX Registry.
TODO:
${configDir}/extensions
by default${configDir}/extensions
by defaultOut of scope:
How to test
Review checklist
Reminder for reviewers