Skip to content

Conversation

renatillas
Copy link
Contributor

@renatillas renatillas commented Sep 29, 2025

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?

@hayleigh-dot-dev
Copy link

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

@renatillas renatillas marked this pull request as ready for review September 29, 2025 18:25
@renatillas
Copy link
Contributor Author

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!

@Kacaii
Copy link

Kacaii commented Oct 8, 2025

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants