Description
There are some key differences between our extension headers, and that of vscode, namely:
globe icon (not sure as to what the reason might be - perhaps global install?)~license field (brackets has a license in open-vsx but none is shown in the editor)~: #7381_Theia_
_VS Code_
@kaiyue0329 would you like to address the issue?
The license bug might be related to:
we include a globe icon (not sure as to what the reason might be - perhaps global install?)
global means that namespace is not claimed and anyone can publish, please read tooltip on hover
we omit data, for example the license field (brackets has a license in open-vsx but none is shown in the editor)
Because of https://github.com/eclipse-theia/theia/issues/7381?
we include a globe icon (not sure as to what the reason might be - perhaps global install?)
global means that namespace is not claimed and anyone can publish, please read tooltip on hover
I was wondering it it made sense for end-users to see this info?
I understand it is present in the open-vsx, but is it useful for end-users?
we omit data, for example the license field (brackets has a license in open-vsx but none is shown in the editor)
Because of #7381?
Right, I mentioned it https://github.com/eclipse-theia/theia/issues/7434#issuecomment-605048757
I understand it is present in the open-vsx, but is it useful for end-users?
Yes, it is important that one who instals was aware that an extension is not published by verified author but by some person on the internet.
I understand it is present in the open-vsx, but is it useful for end-users?
Yes, it is important that one who instals was aware that an extension is not published by verified author but by some person on the internet.
Thank you for clarifying for me :)