getChatMessages respects audience content type and id #9628
Conversation
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
|
rickyrombo
approved these changes
Sep 4, 2024
audius-infra
pushed a commit
that referenced
this pull request
Sep 5, 2024
[0902048] Add stems api for v1 (#9513) Raymond Jacobson [dda5524] Add createUserBankIfNeeded call to trending rewards bug (#9634) Raymond Jacobson [b80df23] Revert "Cycle solana RPC connections better (#9147)" (#9635) Raymond Jacobson [adf2207] [PAY-3370] Always use encoded content IDs in chats (#9636) Reed [53e78ae] getChatMessages respects audience content type and id (#9628) Reed [355c7a9] [QA-1512] Mediorum transcode fixes (#9631) Steve Perkins
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Previously all purchase/remix blasts were showing the same messages even if specific contents had been selected. Update the queries to take
audience_content_typeandaudience_content_idinto account.How Has This Been Tested?
Tested locally, confirmed 2 purchase blast threads with different contents were separate.