Add the thread participant fields sent by the real backend - #56
Open
gpunto wants to merge 1 commit into
Open
Conversation
gpunto
marked this pull request as ready for review
August 7, 2026 10:55
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.
🔗 Issue Links
Needed by GetStream/stream-chat-android#6620, which migrates Android's thread participants to the OpenAPI-generated
ThreadParticipantmodel./threadsis synthesised insrc/helpers/threads.rbrather than recorded bysync.rb(threads have to be derived from the messages each test creates), and the synthesisedthread_participantshad drifted from the real payload: it carried onlyuser_idanduser.The real backend also sends
app_pk,channel_cid,thread_id,created_at,last_read_at,last_thread_message_atandcustom— all of which the OpenAPI spec marks required onThreadParticipant. Clients generated from the spec therefore fail to decode the mock response.This adds those fields, derived per participant from that user's own replies. The change is purely additive — no existing field is renamed or removed — so SDKs that don't read them are unaffected.
🧪 Testing Notes
Please verify the E2E test runs: