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
Just a quick question, and since I haven't found a better place to ask (is there one?): are there plans already when the extension could move out of pre-release?
I have a VSCode extension here (https://marketplace.visualstudio.com/items?itemName=floooh.vscode-kcide) which is now pretty much ready to use. The extension runs a cmdline assembler tool via the WASI extension and it's working fine. The only downside is that users must install the extension as pre-release, otherwise installing the ms-vscode.wasm-wasi-core extension won't work.
Even though I mention that caveat promimently in the documentation, users are still likely to stumble over that problem since it differs from how VSCode extensions are usually installed.
IMHO, releasing a non-prerelease version of the WASI extension wouldn't be much of a problem if the major version number stays at 0, and the extension is marked as "Preview" in the marketplace?
The text was updated successfully, but these errors were encountered:
Just a quick question, and since I haven't found a better place to ask (is there one?): are there plans already when the extension could move out of pre-release?
I have a VSCode extension here (https://marketplace.visualstudio.com/items?itemName=floooh.vscode-kcide) which is now pretty much ready to use. The extension runs a cmdline assembler tool via the WASI extension and it's working fine. The only downside is that users must install the extension as pre-release, otherwise installing the
ms-vscode.wasm-wasi-core
extension won't work.Even though I mention that caveat promimently in the documentation, users are still likely to stumble over that problem since it differs from how VSCode extensions are usually installed.
IMHO, releasing a non-prerelease version of the WASI extension wouldn't be much of a problem if the major version number stays at 0, and the extension is marked as "Preview" in the marketplace?
The text was updated successfully, but these errors were encountered: