You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Take cleared_history_at into account in chatUpdateLatestFields when deciding whether to set chat_member.is_hidden to false.
Only set is_hidden to false if there exist messages or reactions that were sent aftercleared_history_at.
How Has This Been Tested?
Tested on local stack:
artist deleting convo indeed hides convo, even after sending more blasts
fan reacting/responding still unhides chat for artist
fan reacting to older messages than artist's cleared_history_at - chat remains hidden for artist
fan clearing history - only shows blasts after cleared_history_at
Note: I tested one case that still is a bit off: fan clears history, artist sends blast: chat is still hidden on fan side. Then artist sends another blast, now chat is unhidden for fan. Not entirely sure why this is, but i think this is good enough for now - 2nd blast or message from artist will come thru, and if fan refreshes they will see the chat.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
[2999fcc] Re-enable payment router tests after network cut (#9926) Marcus Pasell
[39c02a4] Add distro sources (#9908) Steve Perkins
[0ee4515] [PAY-3463] Chat is_hidden respects cleared_history_at (#9919) Reed
[f807632] Only send blast notifs when no existing chat (#9916) Reed
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
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
Take
cleared_history_atinto account inchatUpdateLatestFieldswhen deciding whether to setchat_member.is_hiddento false.Only set
is_hiddento false if there exist messages or reactions that were sent aftercleared_history_at.How Has This Been Tested?
Tested on local stack:
cleared_history_at- chat remains hidden for artistcleared_history_atNote: I tested one case that still is a bit off:
fan clears history, artist sends blast: chat is still hidden on fan side. Then artist sends another blast, now chat is unhidden for fan. Not entirely sure why this is, but i think this is good enough for now - 2nd blast or message from artist will come thru, and if fan refreshes they will see the chat.