-
Notifications
You must be signed in to change notification settings - Fork 63
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
Latest plugin changes are not available in the VS marketplace #62
Comments
I can perform an update this weekend. Ideally we move the plugin to a shared organization or something with similar capabilities as currently the above link is on my personal account. I had looked at this in the past but there were some issues when adding people. I will have another look so it isn't dependent solely on me. |
@tiehuis I think we could deprecate the extension under your account and create an official one instead. Like this one: FYI: |
Is there an timeline? Looking forward to the official VSCode extension. |
@tiehuis I made an account for Zsf and tried to publish the extension as |
I will do this tonight. Ping me again if I am slow. |
I have updated the tiehuis.zig extension to 0.2.6, which now points to tiehuis/vscode-zig repo which should free up the above. I have not updated to latest master on this packaged extension yet. Would prefer to deprecate and in favor of ziglang/vscode-zig. |
I am open to updating the extension for the moment however. I new version would be good to cut first before this is done that is shared between the two if so. |
@Vexu would you be able to bump the version to latest when publishing first official extension? |
ping.... |
I'm still getting the same error, I'll ask for help in the marketplaces repo. |
Extension is now released as https://marketplace.visualstudio.com/items?itemName=ziglang.vscode-zig, |
cc @tiehuis |
According to marketplace last updated field, the plug-in is not being updated.
For example, the "problem matcher" feature is simply unavailable.
The text was updated successfully, but these errors were encountered: