Messaging client: handle last unfollowed message date/time when outside communication is sent #78
Conversation
This file contains 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
…de communication is sent
mcjustin
approved these changes
Nov 10, 2023
achen2401
deleted the
feature/handle-last-unfollowed-message-datetime
branch
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.
part of https://www.pivotaltracker.com/story/show/185895123
change includes:
If an outside communication is sent via the Messaging client app and the date/time of this outside communication does not pre-date the datetime of existing
time-of-last-unfollowed-messageextension, the recipient'stime-of-last-unfollowedup-messageextension datetime will be updated to2025-01-01T00:00:00Z(implying that there is no unfollowed message; the date/time is a future date/time so thatTime since replycolumn can be displayed/sorted correctly.)