Repository navigation
Move message, reaction, reply, translate and action endpoints to v2 - #6837
Conversation
PR checklist ✅All required conditions are satisfied:
🎉 Great job! This PR is ready for review. |
SDK Size Comparison 📏
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Priority: ⬇️ Low Merge Risk: ⚪ Minimal · up to
|
andremion
left a comment
There was a problem hiding this comment.
Looks good. Two notes inline, both optional.
|
|
🚀 Available in v7.15.0 |



Goal
Move the message endpoints to v2: send, get, update, partial update, delete, actions, reactions, reaction queries, replies and translations. The websocket stays on v1.
Part of AND-1637
Implementation
MessageApiis built on/api/v2/chat/.... v2 nests custom data undercustom, so a sent or updated message and a reaction keep their custom data.extraData(mml,poll_id,mentioned_group_ids,restricted_visibility). They go back to their typed fields. The response-only ones (draft,image_labels) are dropped, since the backend would store them as custom data.Testing
V2LaneBatchFiveTestparses the v2 message, reply, reaction and translation responses and checks the request bodies.DtoMappingTestcovers the declared fields sent back as typed fields.Summary by CodeRabbit