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

🆕 Read marker handling based on ID and settable via API #1214

Merged
merged 6 commits into from
Jul 25, 2019

Conversation

nickvergessen
Copy link
Member

@nickvergessen nickvergessen commented Sep 26, 2018

  • Fix writing of last_mention_message
  • Add endpoint to set the last_read_message
  • Adjust unit tests
  • Correctly set the read marker from the web UI
  • Fix the loading of the chat messages as described in Chat flow experience #1164
  • People added later should have the marker set to !== 0 so they are at the bottom and not the start.

Rel #1164
Rel #1788

@nickvergessen nickvergessen added 2. developing feature: chat 💬 Chat and system messages feature: api 🛠️ OCS API for conversations, chats and participants labels Sep 26, 2018
@nickvergessen nickvergessen added this to the 💚 Next Major milestone Sep 26, 2018
@nickvergessen nickvergessen self-assigned this Sep 26, 2018
@nickvergessen nickvergessen force-pushed the feature/noid/unread-message-marker branch from d379cd6 to 14bb2f8 Compare September 27, 2018 10:00
@nickvergessen
Copy link
Member Author

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 setReadMarker=0 (see docs) and instead manually set it via Mark chat as read. This would allow to fetch messages, but only update the read marker when you scroll to actual new messages.

Signed-off-by: Joas Schilling <[email protected]>
@nickvergessen nickvergessen force-pushed the feature/noid/unread-message-marker branch from 99d1b67 to 30c5d02 Compare July 24, 2019 13:37
@nickvergessen nickvergessen changed the title Unread message marker Read marker handling based on ID and settable via API Jul 24, 2019
@nickvergessen nickvergessen changed the title Read marker handling based on ID and settable via API 🆕 Read marker handling based on ID and settable via API Jul 24, 2019
@nickvergessen nickvergessen changed the title 🆕 Read marker handling based on ID and settable via API 🏷 Read marker handling based on ID and settable via API Jul 24, 2019
@nickvergessen nickvergessen changed the title 🏷 Read marker handling based on ID and settable via API 🆕 Read marker handling based on ID and settable via API Jul 24, 2019
Copy link
Member

@Ivansss Ivansss left a 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

@nickvergessen nickvergessen merged commit db48265 into master Jul 25, 2019
@delete-merged-branch delete-merged-branch bot deleted the feature/noid/unread-message-marker branch July 25, 2019 11:48
@nickvergessen nickvergessen mentioned this pull request Jul 25, 2019
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review feature: api 🛠️ OCS API for conversations, chats and participants feature: chat 💬 Chat and system messages high
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants