Open eladb opened 1 month ago
It takes a few seconds to get the tunnel created and the app restarted and there's no clear indication what's happening (perhaps some kind of modal loading window or some other indication that the app is being restarted).
+100 And plus 1 for the other stuff
Just adding to this, I'm still new to the whole thing, and agree on what's already been said.
Also stopping my wing console with an active tunnel kills the tunnel (expected), when I start the console again the tunnel is back to active. But only a small indication in the UI that this is the case.
Could this catch people out? Folks that open a tunnel, close the console, and open in the future to have an open tunnel they forgot about? Just a thought...
I'm adding some UI/UX improvements to the endpoints here https://github.com/winglang/wing/issues/6796
Only missing this part:
We should get the user to approve that they understand the security implications of a tunnel into their local machine.
We should get the user to approve that they understand the security implications of a tunnel into their local machine.
Maybe we could use our local config object to store whether the user approved the use of tunnels or not, so we only show it once.
It takes a few seconds to get the tunnel created and the app restarted [...]
Not sure if we could also make it faster somehow? Is there room for quick improvements there, @eladcon ?
As @boyney123 mentioned, tunnels are re-exposed when reopening the Console if they were not closed before the Console was last closed.
I think we should show a notification in that case when opening the Console:
I tried this:
Create a tunnel in Wing Console
This happened:
I expected this:
No response
Is there a workaround?
No response
Anything else?
No response
Wing Version
No response
Node.js Version
No response
Platform(s)
No response
Community Notes