-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
Comms for support of deprecated extensions #2750
Comments
|
Thanks for drafting those up @kineticsquid, including the Wiki page, they look great. Should we also mention on the wiki that the |
@filiptronicek Re malicious extensions. I thought about that but decided to not include it because we, thankfully, don't have any yet. I think when we'll add it and document it then. I'm all for robust documentation and I certainly don't mind drafting pages for the wiki. Are you talking about documenting calls like @amvanbaren discusses in eclipse/openvsx#432? Or something else? |
Sounds good, let's add them then.
I am talking about the native integration in VS Code, as shown in the screenshots on microsoft/vscode-discussions#1 (comment). It's what Microsoft does with its list and what participating forks (which AFAIK is only Gitpod's at the moment) use to suggest alternatives to deprecated extensions and uninstall malicious ones. |
@filiptronicek What's the best way to get a full list of the URLs needed for this integration, that are not part of our document API? |
@filiptronicek Let's take what you describe above in #2750 (comment) to a separate enhancement request in https://github.com/eclipse/openvsx. Is this just a documentation effort, or are there enhancements we need to make? |
We need to prepare communications to go along with the support for deprecated extensions in #1121. To wit,
extensions.json
file. I'm thinking a page in the wiki linked to from the main doc page: https://github.com/eclipse/openvsx/wiki.The text was updated successfully, but these errors were encountered: