vscode: enable-proposed-api in argv.json doesn't work in Stable

I don’t get it… How do you feed proposed api to users?

When using combo Insiders + proposed api - that means the extension can break every single day (update of vscode) in turn breaking the extension and you need to update the extension very often? It also means forcing users to use Insiders version which has its own issues.

On the other hand using Stable version + proposed api - means you can test the extension once a month before Stable release and know that it will still work.

It’s not possible to publish proposed api extension to Marketplace, so I don’t actually see it working smoothly for users.

Instead, would it make sense to move simple proposals faster? For instance, this issue #32813 was implemented in December 2019, and had almost no changes, but it’s still in a proposed state. Kind of feels like it’s only moved to stable when you ping the assingee a magic number of times to annoy them enough 😅. If it’s not ready, it would be great to know what blocks it, or to know an approximate date.

Relevant code seems to be here:

https://github.com/microsoft/vscode/blob/df5d0e588ff6956c812b617895e4598ade4db428/src/vs/workbench/services/extensions/common/abstractExtensionService.ts#L479-L486

If I understand correctly, we only do not allow stable to develop on an extension with proposed API.

If there is a bug here then maybe something broke with regards to pushing args into the process in main.js and the renderer not being able to read it out from environmentService.extensionEnabledProposedApi.

@JacksonKearl maybe something to investigate and then reopen this issue for consideration.