-
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
[Plugin Registry] [airgap] Each plugin should display proper icon #14510
Comments
|
Licensing of what? |
@vitaliy-guliy : I guess question from @tolusha is more about are we authorized to pull the images this way. I guess that if we are pulling from the repository it is fine. Another aspect is how this would work if you are behind a proxy and can't reach github? Would it not be better to have that in the meta.yaml and directly in the plugin registry? |
See also #15581 re: icons in devfiles |
Yes, icons should be cacheable inside the registry, just like .vsix files. |
hello @vitaliy-guliy do you have any plans to implement that ? |
Hello, first step, let's have the icons in the plugin registry like we do for devfile registry https://github.com/eclipse/che-devfile-registry/tree/master/images. |
The blocker issue for this is in how these images are retrieved; unless we want to ensure relative links are supported everywhere a plugin icon might be displayed, #15091 needs to be resolved before we throw icons into the registry. |
@sunix why not to point on the image on plugin repository on GitHub? For each plugin we specify its source repository, which almost always contains the plugin logo. |
@vitaliy-guliy ok what ever, as long as this is working :) |
This was fixed in 7.18 but was never closed. |
Thanks |
Is your enhancement related to a problem? Please describe.
On the plugin registry each plugin refers on the same default icon. When displaying them on the UI, it looks not pretty nice
Describe the solution you'd like
We can apply the proper icons for each plugin.
Most of the plugins are VS Code extensions. Most of them are opensource with repository on GitHub. Each extension has
package.json
containsicon
field which refers on the image hosted on that repository. We can easily refers on that images.In result we may have the following
The text was updated successfully, but these errors were encountered: