Skip to content
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.

Sign up for GitHub

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

Jump to bottom

A way to use TypedMessenger without responses #365

Closed
jespertheend opened this issue Jan 28, 2023 · 0 comments · Fixed by #772
Closed

A way to use TypedMessenger without responses #365

jespertheend opened this issue Jan 28, 2023 · 0 comments · Fixed by #772
Assignees
@jespertheend
Labels
effort: Moderate Will take a good amount of time and experience with the codebase, but feasible.
Milestone
MVP

Comments

@jespertheend
Copy link
Collaborator

Especially WebSocket connections often send messages that are more like events, and don't need to wait for a response from the client. It would be nice to still be able to use the TypedMessenger for this since it makes it very easy to add types to the messages.

This will likely change the api in some way so we'll want to do this sooner rather than later.
@jespertheend jespertheend added the effort: Moderate Will take a good amount of time and experience with the codebase, but feasible. label Jan 28, 2023
@jespertheend jespertheend added this to the MVP milestone Jan 28, 2023
@jespertheend jespertheend mentioned this issue Jan 28, 2023
Closed
@jespertheend jespertheend self-assigned this Oct 7, 2023
This was referenced Oct 7, 2023
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jespertheend jespertheend

Labels
effort: Moderate Will take a good amount of time and experience with the codebase, but feasible.
Projects
None yet
Milestone
MVP
Development

Successfully merging a pull request may close this issue.

feat(TypedMessenger): Add response options jespertheend/Renda
1 participant
@jespertheend