-
Notifications
You must be signed in to change notification settings - Fork 450
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
🆕 Read marker handling based on ID and settable via API #1214
Conversation
d379cd6
to
14bb2f8
Compare
3845d9c
to
30ae8fb
Compare
30ae8fb
to
3381c26
Compare
3381c26
to
bd14622
Compare
bd14622
to
30c6d8b
Compare
Signed-off-by: Joas Schilling <[email protected]>
30c6d8b
to
54692eb
Compare
Signed-off-by: Joas Schilling <[email protected]>
Signed-off-by: Joas Schilling <[email protected]>
Ready to review now, because it is a pre-requirement to #2020 The behaviour is the same as before, unless a client wants to handle read-marking themselves. Then they just await new messages with |
Signed-off-by: Joas Schilling <[email protected]>
99d1b67
to
30c5d02
Compare
Signed-off-by: Joas Schilling <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🐘
Doesn't seem to break anything
Signed-off-by: Joas Schilling <[email protected]>
!== 0
so they are at the bottom and not the start.Rel #1164
Rel #1788