docs: cover the moderation tail in the stream-chat-go migration guide - #136
Merged
Conversation
Adds the moderation operations the guide did not document yet: user blocking, blocklists, flagging, and reviewing flagged content. Two things worth calling out for anyone migrating: - Blocklist types are spelled BlockList in the new SDK, so every method renames (CreateBlocklist to CreateBlockList, ListBlocklists to ListBlockLists, and so on). - The legacy flag methods write to the v1 chat flags store while this SDK exposes v2 moderation, so flagging and querying can end up on opposite sides of that boundary. The guide now warns about it, and documents the v1 flag-report workflow as a redesign onto the v2 review queue rather than a rename. All before and after snippets were compiled against stream-chat-go v8 and getstream-go v5 respectively.
mogita
temporarily deployed
to
feeds-enabled-shard
August 1, 2026 10:42 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
mogita
temporarily deployed
to
feeds-enabled-shard
August 1, 2026 10:42 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
mogita
temporarily deployed
to
feeds-enabled-shard
August 1, 2026 10:42 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
mogita
temporarily deployed
to
feeds-enabled-shard
August 1, 2026 10:42 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
mogita
temporarily deployed
to
feeds-enabled-shard
August 1, 2026 10:42 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
mogita
temporarily deployed
to
feeds-enabled-shard
August 1, 2026 10:42 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
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
1 participant
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.
Adds the moderation operations the migration guide did not document yet, so a Chat + Moderation integration has a documented path rather than a gap: user blocking, blocklists, flagging, and reviewing flagged content.
Worth a look during review
Blocklist is spelled
BlockListin this SDK. Every method renames with it (CreateBlocklisttoCreateBlockList,ListBlockliststoListBlockLists). Easy to miss, and it makes the migration look like a missing feature when it is really a rename.Flags cross a v1/v2 boundary. The legacy
FlagMessage/FlagUserwrite to the v1 chat flags store, while this SDK exposes v2 moderation viaModeration().Flag(). As the note inchat_misc_integration_test.goalready says,QueryMessageFlags(v1) may not see flags created through v2. Swapping the call alone can leave a workflow writing to one store and reading from another, so the guide now warns and tells the reader to migrate flag/query/review together.Flag reports are a redesign, not a rename.
QueryFlagReportsandReviewFlagReporthave no drop-in replacement; they map onto the v2 review queue (QueryReviewQueue,GetReviewQueueItem,SubmitAction). Documented as rework rather than a call swap.Verification
Every before and after snippet in the new sections was compiled: the before code against
stream-chat-gov8 and the after code againstgetstream-gov5. That caught two real errors before commit (SubmitActionRequest.ItemIDis a*string, andBlocklistCreateRequestembedsBlocklistBase).Context: this guide is the source of truth for the SDK migration skill being built in
GetStream/agent-skills, so gaps here become gaps a customer hits.