-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Add tunnel activation event #188730
Comments
I like the ports view idea. Let's just go with that for now. There is the possibility that an extension might call |
Do we need this for July? |
I don't think so |
The activation event will be called |
* Add tunnel activation event Fixes #188730 * Refactor
This bug has been fixed in the latest release of VS Code Insiders! @connor4312, you can help us out by commenting If things still don't seem right, please ensure you're on version f7973f3 of Insiders (today's or later - you can use Happy Coding! |
I can |
The built in tunnel forwarding extension can be used to verify this. If you can forward a port when not connected to a remote, then this is verified. |
With #188270, extensions can now contribute tunnel factories. However, extensions doing this need to get activated on
*
/ startupFinished to be shown there. It'd be nice if there was some kind of "tunnel" activation event that would only pick up when a tunnel or requested, or perhaps if the Ports view is interacted with, to avoid this.Mentioned in https://github.com/microsoft/vscode-remote-tunnels/pull/661#discussion_r1272804131
The text was updated successfully, but these errors were encountered: