Repository navigation
Change the publishId in VS Code marketplace #690
Description
Activity
When I discussed with them, I got the opinion to keep the current id for users' experience.
But I'll ask again about differences with your examples.Thank you all for your continued work.
Looking at the Prettier extension, it seems that the ID of the extension remains the same
even if the publisher is changed. If it is changed, will it affect the user?
@eitsupi Thanks for pointing out. Looks like the case of changed publishId is quite few?
publishidand author are different.
Changingauthor, does not have any impact on the user.
I think,Yuki Uedato beREditoris enough.- "author": "Yuki Ueda", + "author": "REditor", "license": "SEE LICENSE IN LICENSE", "publisher": "Ikuyadeu",
Reacted by eitsupiTo be consistent with the organization name and vscode-r-lsp, the author should be "REditorSupport".
The Prettier extension seems to have changed publishers in March of this year when it was no longer in beta?
prettier/prettier-vscode@78ae1a5It seems that the Prettier extension has changed its publisher several times between
esbenpandprettierin order to publish the development version as a separate ID, and the stable version has not changed fromesbenp.
https://marketplace.visualstudio.com/items?itemName=prettier.prettier-vscode
https://marketplace.visualstudio.com/items?itemName=prettier.prettier-vscode-betaFrom the existing cases, it looks like we might better stick to the current publishId and only update the author.
Thanks for initiating the discussion. Looks like we could stick with the current publisher for now.
We could consider it again in the future if there is a necessity (e.g. cannot publish releases). An alternative but less ideal solution is to publish a new extension under REditorSupport and deprecate this extension.
Reacted by Don JayamanneIt seems changing the author of a package is not enough to change the display name on the extension page.
For the case of https://marketplace.visualstudio.com/publishers/esbenp. The publisher id is
esbenpand the display name is "Prettier".
It is possible for @Ikuyadeu to change his display name to "REditorSupport" but I wonder if he wants to do it because it would apply to all his other extensions.@Ikuyadeu, do you mind transferring the extension to the publisher REditorSupport which you are already one of the owners alongside @renkun-ken and me.
It is possible for @Ikuyadeu to change his display name to "REditorSupport" but I wonder if he wants to do it because it would apply to all his other extensions.
I can not change my display name, because I have other extensions that are crated with other teams.
@Ikuyadeu, do you mind transferring the extension to the publisher REditorSupport which you are already one of the owners alongside @renkun-ken and me.
I already send the request to the Microsoft microsoft/vsmarketplace#133 microsoft/vsmarketplace#142
I recall that we did the transfer of vscode-r-lsp via email. Perhaps you could send an email to [email protected] to initiate the transfer.
Hi VS Code PM here 👋
I apologise that the Marketplace team did not respond to your request.
Can the current extension author please email [email protected] and make sure to include me [email protected] in the email.We can easily move your extension to your publisher, however please note that if there are current extension packs or extension dependencies on your extension they will have to get updated.
Extension recommendations also need to be updated, but I can easily do that on the VS Code side to take into account the new publisher id.Reacted by Prashant Cholachagudda, Yuki Ueda, Randy Lai and Gustavo VelásquezHi VS Code PM here 👋
I apologise that the Marketplace team did not respond to your request. Can the current extension author please email [email protected] and make sure to include me [email protected] in the email.
We can easily move your extension to your publisher, however please note that if there are current extension packs or extension dependencies on your extension they will have to get updated. Extension recommendations also need to be updated, but I can easily do that on the VS Code side to take into account the new publisher id.
Thank you for your response.
Now, I send the e-mail from [email protected]Reacted by Kun Ren, Isidor Nikolic, Randy Lai and Gustavo VelásquezJust notice that the publisher id of the extension has been updated:
https://marketplace.visualstudio.com/items?itemName=REditorSupport.r
I wonder if there's anything broken on user side?
Reacted by eitsupi, Gustavo Velásquez, Randy Lai and Yuki UedaI was wondering why the R extension was not automatically installed when I rebuilt Dev Container last night.
Definitely an effect of the ID change.In other words, if the ID is specified in
settings.json, etc., it would be affected.Perhaps it would be a good idea to announce in the README or elsewhere that the ID has been changed.
Perhaps it would be a good idea to announce in the README or elsewhere that the ID has been changed.
Yes. I'll include it in the NEWS in the next release.
Reacted by eitsupi and Randy LaiFYI, after rewriting the ID in
devcontainer.json(toreditorsupport.r), it is now installed automatically again.When I click
Install in SSH:...in vscode which has a reditorsupport.r installed locally when using remote ssh, it installsikuyadeu.r.When I click
Install in SSH:...in vscode which has a reditorsupport.r installed locally when using remote ssh, it installsikuyadeu.r.It should work if you uninstall the extension on both local and remote machine, reload vscode, and install again.
No. It doesn' t work for me. I also tried removing
.vscode-server/extensions/ikuyadeu.r-2.4.0/and.vscode-server/. It still would installreditorsupport.rlocally andikuyadeu.rremotely.Even I download vsix from https://github.com/REditorSupport/vscode-R/releases/tag/v2.4.0 and use "install with VSIX" menu it would show as
ikuyadeu.rand the R activity bar icon cannot be shown.The reason for this is that the latest published extension version still has the
publisher: ikuyadeuin thepackage.json.
@renkun-ken To fix this the extension simply needs to publish a new version (since the publisher is already fixed on the main branch).A new version is released. @isidorn You could take a look if this still happens.
Reacted by Yuki Ueda@renkun-ken thanks! @xgdgsc can try it out and let us know.
Since the project has been transferred to REditorSupport as suggested in #98, we may better have a discussion on the issue of changing publishId in the VS Code marketplace here.
When the repo is transferred, the following are examples for both sides: changing or keeping the publishId.
Changed:
Unchanged: dbaeumer.vscode-eslint, esbenp.prettier-vscode
Some related issues: