Migrate channel update and member request bodies to the generated UpdateChannelRequest model - #6629
Migrate channel update and member request bodies to the generated UpdateChannelRequest model#6629gpunto wants to merge 1 commit into
Conversation
PR checklist ✅All required conditions are satisfied:
🎉 Great job! This PR is ready for review. |
SDK Size Comparison 📏
|
2cf3baa to
4ba4272
Compare
…ateChannelRequest model
4ba4272 to
e114121
Compare
|
Parking this until the OpenAPI spec generator is fixed.
Reopening once the spec emits |
|
|
Superseded by #6634 (this PR cannot be reopened after the branch was force-pushed). |


Goal
Migrate the channel update and member request bodies to the generated
UpdateChannelRequestmodel.Part of AND-1291
Implementation
UpdateChannelRequest:AcceptInviteRequest,RejectInviteRequest,AddMembersRequest,RemoveMembersRequest,InviteMembersRequestand the oldUpdateChannelRequest. The endpoint takes one shape, so theseparate wrappers collapse into it.
MessageRequest,ChannelInputRequest,ChannelMemberRequest,Attachment,Action,Field,Images,ImageData,SharedLocation,ConfigOverridesRequestandUserResponse.Message.toMessageRequest()for the system message these endpoints can carry, plusMessageRequestAdapter,AttachmentRequestAdapter,ChannelMemberRequestAdapterandChannelInputRequestAdapterso custom data is flattened to the root on the way out.Testing
UpdateChannelRequestAdapterTestcovers the serialized body for each of the collapsed calls, includingthe flattened custom data.