You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to pass the --enable-proposed-api flag to vscode
I'm using this patch 9fb33dc
I've also added myextension.id to extensionAllowedProposedApi.
Tried executing via below however it doesn't look like that argument is passed to vscode.
fwiw I suspect #1779 is a different issue since that's for enabling the proposed API in the client/web worker host rather than the server-side host. The error also looks unusual and I think it might be specific to the remote extensions so there might not be anything we can do about it, but I think it's worth a check to make sure it's not a bug on our end.
nvm, I completely misremembered, it's just that the web handles it differently than the local version and has nothing to do with the extension hosts. #1744
Very possible that resolving #1744 via #1779 will fix this then, apologies for the noise. 😊 It's still odd that the error is different but we'll see how it goes.
Activity
nhooyr commentedon Aug 20, 2020
See #1779
code-asher commentedon Aug 24, 2020
fwiw I suspect #1779 is a different issue since that's for enabling the proposed API in the client/web worker host rather than the server-side host. The error also looks unusual and I think it might be specific to the remote extensions so there might not be anything we can do about it, but I think it's worth a check to make sure it's not a bug on our end.
code-asher commentedon Aug 24, 2020
A bit more context, @JayDoubleu got this error after including the changes in #1779. (Correct me if I'm wrong though!)
code-asher commentedon Aug 24, 2020
nvm, I completely misremembered, it's just that the web handles it differently than the local version and has nothing to do with the extension hosts. #1744
Very possible that resolving #1744 via #1779 will fix this then, apologies for the noise. 😊 It's still odd that the error is different but we'll see how it goes.
nhooyr commentedon Aug 31, 2020
v3.5.0 with VS Code v1.48.2 has been released, fixing this issue! 🍻