Closed isidorn closed 2 years ago
@isidorn Thank you for your feedback . This seems more like a product update request on our side due to a breaking change on your side . We will try to engage with the relevant team offline and will update .
@shashishailaj thank you. I am also in an email thread with @robotdad
@isidorn Thanks for letting us know that you are in contact with Marc. Since this is not related to any specific doc and is more of a product update, we will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.
Thank you
Hi VS Code PM here 👋
We are changing how proposed API in VS Code can be used. The gist is that
enableProposedApi
has been replaced withenabledApiProposals: […]
and thatvscode.proposed.d.ts
has been replaced with adts
-file per proposal. This enables fine grained control and allows to scope proposals to selected extensions. You can read up on all the details here: https://github.com/microsoft/vscode/issues/131165Action required: Follow the migration guide at https://github.com/microsoft/vscode/issues/136964 and update your extension timely. Find a sample adoption here or here. Your extension should be updated in time for our Jan 2022 release (shipping early Feb 22), it is safe to make the changes immediately, also know that your extension stays backwards compatible.
Also note that for future use of different proposals you need to reach out to us. There is no more wildcard access to all proposals, instead proposals must be spelled out in our
product.json
-file.Let us know if you have any questions.
If the sphere extensions are no longer using proposed API just let me know and that is the best outcome actually
Thanks.