Closed asudox closed 6 months ago
This is intentional behaviour as the 'mentions' field is meant to be interpreted as the users that the message notified at the time of sending. Calculating the current mentions list should be relatively cheap for the receiving client if necessary.
I'm going to close this out unless if others chime in and agree this should be changed, I would probably recommend proposing this change as an RFC for further discussion if there is interest.
What happened?
When a user sends a message and then edits the message to include a mention, the API does not return a
mentions
field containing the mention in the message object. Furthermore, when a message with a mention gets a new mention via editing, the new mention is completely ignored and the mention before the new mention was edited in is included in the mentions field. Regardless, the new mention is visible in the content field.API response of a message without a mention:
API response of the same but edited message that has a mention in it:
As you can see above, the mention is visible in the content field, but no mentions field is supplied with the API response.
API response of a message with a mention:
API response of the same but edited message that now has another mention in it:
The new mention is visible in the content field but the mentions field is not updated to contain the new mention.
Expected Result: The API should return a mentions field that contains all mentions present in the message, including those added after the initial message was sent.