VSCodium / vscodium

binary releases of VS Code without MS branding/telemetry/licensing
https://vscodium.com
MIT License
25.63k stars 1.12k forks source link

Better represent publishers of extensions #2043

Open kineticsquid opened 1 month ago

kineticsquid commented 1 month ago

This is similar to an issue I opened in Theia: https://github.com/eclipse-theia/theia/issues/14240.

Open VSX differs from the VS Code Marketplace in that Open VSX distinguishes between a publisher and a name space. VS Code Marketplace does not make this distinction. On Open VSX, one can see an extension's name, namespace and publisher. E.g.:

image

However, when an extension is shown in VS Codium, this distinction is lost and only the namespace is displayed. Same as in Theia, but it adds a publisher tooltip.

image

This is misleading because it would appear that this extension was published to Open VSX by ms-python (Microsoft). When it was published by the open-vsx admin account.

My suggestion would be to replace the extension namespace with the publisher both on the extension details page and on the list of extensions:

image
daiyam commented 1 month ago

My suggestion would be to replace the extension namespace with the publisher both on the extension details page

While I can understand that, ms-python is still the author of the extension, not open-vsx. It would also be confusing for those used to VSCode.

And finally, I wouldn't like my extensions to not use my namespace (which is the same as on MS Marketplace)

kineticsquid commented 1 month ago

@daiyam Understood. I was looking for a way to reflect the fact that the owner of the ms-python namespace had not published the extension to Open VSX.