paulmataruso/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2025-10-23 04:52:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

message_edit: Add last_moved_timestamp to API message objects.

Browse Source 
This will allow clients to display MOVED/EDITED indicators, and their
tooltips, without interacting with the `edit_history` section of
message objects, which we plan to remove in the future.

Supporting that requires both introducing both last_moved_timestamp,
and changing the definition of last_edit_timestamp to not include
message moves, which involves recalculating it at the API layer.

The last_moved_timestamp is not present if the topic moves for the
message are for resolving or unresolving the topic. It is always
present for channel moves.

Co-authored-by: Lauryn Menard <lauryn@zulip.com>
This commit is contained in:
Tim Abbott
2025-03-06 12:37:30 -08:00
parent a63ab5379e
commit 9849048d6e
6 changed files with 281 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
api_docs/changelog.md
View File

@@ -20,6 +20,25 @@ format used by the Zulip server that they are interacting with.
## Changes in Zulip 10.0
**Feature level 365**
* [`GET /events`](/api/get-events), [`GET /messages`](/api/get-messages),
[`GET /messages/{message_id}`](/api/get-message): Added
`last_moved_timestamp` field to message objects for when the message
was last moved to a different channel or topic. If the message's topic
has only been [resolved or unresolved](/help/resolve-a-topic), then
the field is not present. Clients should use this field, rather than
parsing the message object's `edit_history` array, to display an
indicator that the message has been moved.
* [`GET /events`](/api/get-events), [`GET /messages`](/api/get-messages),
[`GET /messages/{message_id}`](/api/get-message): The
`last_edit_timestamp` field on message objects is only present if the
message's content has been edited. Previously, this field was present
if the message's content had been edited or moved to a different
channel or topic. Clients should use this field, rather than parsing
the message object's `edit_history` array, to display an indicator
that the message has been edited.
**Feature level 364**
* [`PATCH /realm/user_settings_defaults`](/api/update-realm-user-settings-defaults),