Add ways to scope access to proposed API · Issue #131165 · microsoft/vscode (original) (raw)

We have a problem currently that if a first party wants to use one of our "forever proposed APIs" like window.onDidWriteTerminalData, they need to be added to our enable proposed API list which could lead them to accidentally use other proposed API which is likely to change.

This proposal is about adding a new API type which is stable but not accessible to anyone but close friends because of various concerns we have in making the API public. This would help these trusted parties not accidentally jump on proposed API and also help the general public from not trying out these APIs, I still get the occasional issue every now about someone who has tried onDidWriteTerminalData and asking about it being stabilized.