Having chatlist timestamp reflect time of last change #1173
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
…tname, upload bot, etc.)
hathind-ms
approved these changes
May 23, 2023
shawncal
pushed a commit
to shawncal/semantic-kernel
that referenced
this pull request
Jul 6, 2023
…tname, upload bot, etc.) ### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> Having chatlist timestamp reflect time of last change affecting chat (i.e., time bot was uploaded, chat name change, etc.). This value is computed in session only. If session is refreshed, chat list will be ordered timestamp of last message in each chat, with most recent message on top.  Notice difference in timestamp of last message vs timestamp in chatlist (reflects time bot was uploaded)
golden-aries
pushed a commit
to golden-aries/semantic-kernel
that referenced
this pull request
Oct 10, 2023
…tname, upload bot, etc.) ### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> Having chatlist timestamp reflect time of last change affecting chat (i.e., time bot was uploaded, chat name change, etc.). This value is computed in session only. If session is refreshed, chat list will be ordered timestamp of last message in each chat, with most recent message on top.  Notice difference in timestamp of last message vs timestamp in chatlist (reflects time bot was uploaded)
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.
Motivation and Context
Having chatlist timestamp reflect time of last change affecting chat (i.e., time bot was uploaded, chat name change, etc.).
This value is computed in session only. If session is refreshed, chat list will be ordered timestamp of last message in each chat, with most recent message on top.
Notice difference in timestamp of last message vs timestamp in chatlist (reflects time bot was uploaded)