-
Notifications
You must be signed in to change notification settings - Fork 292
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
Upgrade to VS Code's webview API #403
Comments
where is the owner of this repo :) @seanpoulter |
Thanks for the heads up @mjbvz. What do you have in mind for Gitter @nasreddineskandrani? If you're joking that you rely on this extension for your business, I'm happy to help review your PR. |
A gitter channel: Collaborators: the joke was to attract your attention since i found this post important. I thought maybe you ll filter in email your github messages :) ( nice work with this extension, i like it) |
Thanks for the suggestion to use Gitter. I've opened #407 to see who's interested and if they can pay attention to a Gitter channel. It sounds like it could help but I'm worried it'll take our time away from all these Issues and PRs. 😉 Any thoughts on what we need to fix for the webview API? |
Just a heads up: in VS Code 1.32 (the February update), using the previewHtml command will show an alert to the user, although the command should still work. We plan to remove the command entirely with VS Code 1.33 (March update) |
The March update is probably coming soon, any update on this? |
Hi, I'm on the VS Code team. I noticed that your extension uses the
vscode.previewHtml
command which is deprecated and which we are actively working to remove: microsoft/vscode#62630We've developed a webview API that provides a much better developer experience and offers a number of important security and compatibility benefits over
previewHtml
. We cannot fixpreviewHtml
without breaking backwards compatibility, and have instead opted to remove it.To ensure that your extension continues to work properly in VS Code, please try upgrading to use the new Webview API. You can find documentation on the API usage here. Let me know if you have any questions or concerns about this migration
The text was updated successfully, but these errors were encountered: