Skip to content
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

Better represent publishers of extensions #2043

Open
kineticsquid opened this issue Oct 1, 2024 · 2 comments
Open

Better represent publishers of extensions #2043

kineticsquid opened this issue Oct 1, 2024 · 2 comments
Labels
discussion could go either way, discussion welcome

Comments

@kineticsquid
Copy link

This is similar to an issue I opened in Theia: eclipse-theia/theia#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
Copy link
Member

daiyam commented Oct 1, 2024

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)

@daiyam daiyam added discussion could go either way, discussion welcome and removed bug Something isn't working labels Oct 1, 2024
@kineticsquid
Copy link
Author

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion could go either way, discussion welcome
Projects
None yet
Development

No branches or pull requests

2 participants