-
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
vsx: update extension information in the extension-editor #7434
Comments
@kaiyue0329 would you like to address the issue? |
The license bug might be related to: |
global means that namespace is not claimed and anyone can publish, please read tooltip on hover |
Because of #7381? |
I was wondering it it made sense for end-users to see this info? |
Right, I mentioned it #7434 (comment) |
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 :) |
Description
There are some key differences between our extension headers, and that of vscode, namely:
we include aglobe
icon (not sure as to what the reason might be - perhaps global install?)we omit data, for example the: improve license detection for built-in extensions #7381license
field (brackets has a license in open-vsx but none is shown in the editor)Theia
VS Code
The text was updated successfully, but these errors were encountered: