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.

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

Messaging spec #42

Merged
merged 5 commits into from
Feb 2, 2025
Merged

Conversation

geekingfrog
Copy link
Collaborator

An attempt to define the specs for chats. I think we'll add a few other source/target like lobby or party.

(also note, the CI on this project does not like jujutsu created commit :/ )

@p2004a p2004a self-requested a review January 26, 2025 18:58
Copy link
Collaborator

@p2004a p2004a left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How recipient receives the actual message?

@geekingfrog
Copy link
Collaborator Author

How recipient receives the actual message?

omg, I forgot the message property on the messaging/received event -_-"
I have amended the commit to correct that. Also expanded the readme to explain more, let me know if that makes sense.

* drop the `source` from the subscribe request. Will reintroduce later
  when it makes sense.
* default history mode is `latest`
* remove messages from subscribe response
* rename `player_id` to `user_id`
* add timestamp to messages
* change history marker to string. This makes it clearer that it's an
  opaque value, and give more flexibility to the server.
@p2004a p2004a merged commit fdeec3e into beyond-all-reason:master Feb 2, 2025
1 check passed
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