-
Notifications
You must be signed in to change notification settings - Fork 55
Add support for websockets #144
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
base: main
Are you sure you want to change the base?
Conversation
One quite prominent constraint with this implementation is all websocket endpoints must have the same state type. i can think of ways to design applications with this constraint in mind but its still worth bringing to attention |
The PR should be stable enough now for review, sorry for the after-draft commits as I saw flaws in the simulate module I submitted. Thanks in advance for the review! |
d1f811f
to
bd5e9ce
Compare
Sorry! I wasn't sure if it my issue was going to be mentioned here too, If needed lmk and I'll remove it. Im really excited for this new feature <3 |
This is the only way I could implement websockets in a typesafe way, but introducing a breaking change on the response type. What do you think?