When I'm using the sim to test locally it looks like the endpoint for a websocket is updated after a code change compile. The port number is updated whenever a code change is made and the sim compiles the changes. This makes it difficult to do client/API testing and development as the endpoint constantly changes.
This happened:
Port number of the websocket endpoint is updated after a code change compile.
I expected this:
It would be great for the websocket endpoint to remain the same after a code change and sim reload.
Is there a workaround?
Currently I have to update the endpoint in the client after each API code change.
Anything else?
No response
Wing Version
0.84.2
Node.js Version
v20.13.0
Platform(s)
Linux
Community Notes
Please vote by adding a 👍 reaction to the issue to help us prioritize.
If you are interested to work on this issue, please leave a comment.
I tried this:
When I'm using the sim to test locally it looks like the endpoint for a websocket is updated after a code change compile. The port number is updated whenever a code change is made and the sim compiles the changes. This makes it difficult to do client/API testing and development as the endpoint constantly changes.
This happened:
Port number of the websocket endpoint is updated after a code change compile.
I expected this:
It would be great for the websocket endpoint to remain the same after a code change and sim reload.
Is there a workaround?
Currently I have to update the endpoint in the client after each API code change.
Anything else?
No response
Wing Version
0.84.2
Node.js Version
v20.13.0
Platform(s)
Linux
Community Notes