You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, only base Visual Studio Code can install extensions from Checkmarx through the Microsoft extension registry. Forks (such as VSCodium) are prohibited from using the Microsoft marketplace (see microsoft/vscode#31168) so make use of an open registry alternative.
Propose a solution
To support other VSC-based editors, the extension should be published to Open VSX (https://open-vsx.org/).
Additional comments
People are able to manually install the extensions by downloading the individual VSIX packages, but that's not as nice as having in-editor support. I imagine if you were to offer this extension via Open VSX it wouldn't come with the same level of support as VSCode's extension because who knows what forks are doing in their code.
The text was updated successfully, but these errors were encountered:
@jbrotsos I haven't made any charges - fork or otherwise. This issue is about publishing the official Checkmarx extension to the Open VSX repo as well as the official MS VSCode repository to allow other VSCode-based clients to consume the extension (VSCodium in my case).
I could PR in a GitHub action to publish it there (or amend an existing one), but I imagine that someone on the Checkmarx side would need to register with Open VSX and get a token for it before that action is run.
Is your request related to a workflow problem?
Currently, only base Visual Studio Code can install extensions from Checkmarx through the Microsoft extension registry. Forks (such as VSCodium) are prohibited from using the Microsoft marketplace (see microsoft/vscode#31168) so make use of an open registry alternative.
Propose a solution
To support other VSC-based editors, the extension should be published to Open VSX (https://open-vsx.org/).
Additional comments
People are able to manually install the extensions by downloading the individual VSIX packages, but that's not as nice as having in-editor support. I imagine if you were to offer this extension via Open VSX it wouldn't come with the same level of support as VSCode's extension because who knows what forks are doing in their code.
The text was updated successfully, but these errors were encountered: