Repository navigation
feat(chat): adopt the flipcash2 0.21.0 contract - #1840
Merged
Merged
Conversation
Map multi_receiver and payment_request_id into MessageContent.Cash and carry them through the Room serialization.
…ervice Chat: SilenceUser, UnsilenceUser, BanUser, UnbanUser and GetRestrictedUsers through api, service, repository and controller; ViewerState restrictions and Permissions.moderation; BANNED on JoinChat and EnterLobby. PaymentRequest: api, service, repository and controller for the five RPCs, returning generated paymentrequest.v1 types like Poll. PAYMENT_REQUEST widgets map to Unsupported until a UI consumes them. Adds buildRequestedPaymentMetadata for intent ChatMetadata.requested_payment.
github-actions
Bot
added
type: feature
bmc08gt
marked this pull request as ready for review
October 23, 2026 20:48
github-actions
Bot
added
type: feature
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves
flipcash2-client-protocolto0.21.0(code-payments/flipcash2-client-protocol#29) and adapts the app to the new contract. It adds no UI.CashContent: the mappers in both directions follow the renamesamount→total_amountandreceiver→single_receiver. They also carry the newmulti_receiverandpayment_request_idfields, including through Room. Old rows decode with defaults.CashContentMappingTestis new, andChatEntityMapperTestandConversionsTestare extended.BANNED: newBannedcases on the join-chat and enter-lobby errors, mapped inChatService.ViewerState:restrictions(silence) andPermissions.moderationare mapped.SilenceUser,UnsilenceUser,BanUser,UnbanUserandGetRestrictedUsersgo throughChatApi→ChatService→ChatRepository→ChatController.PaymentRequestservice: Api, Service, Repository and Controller for its five RPCs, provided fromFlipcashModule. It follows the Poll* shape, so domain models wait until a UI uses them.ChatMetadata.requested_payment: handled inRequestedPaymentMetadata.kt.PaymentRequestWidgethas no dedicated mapping yet.