-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chat Ordering Newest to Oldest #391
Comments
@smeragoel Any objections here? |
No objections, this is the ideal approach. You have my vote ➕ |
Hey folks, I'm getting up to speed with the codebase and am noticing we don't have any tests in |
Following the discussion started in #445 (comment), we need to define what "newest" and "oldest" mean. There are currently two contenders to order chats:
I initially preferred 1., but I'm leaning towards 2. now for these reasons:
@Adam-D-Lewis Since you have reported this, what would you prefer? |
Option 2 so you see the chat with the most recent message at the top would be my preference. |
Based upon my experience of using these LLM interfaces, I could easily identify that the approach they follow is that they sort the chat order based upon the last usage of the chat. |
Sorry, I should have been more clear. A screenshot or even your testimony would have been sufficient. I just want to make sure if we make a change here, that we not deviate from what others are doing without a clear reason to do so. |
Totally no worries. I'm pretty sure that our approach is aligned with what others are doing already. I also did some workaround for the same in #445 & now i can see chats being ordered based upon the last usage of the chat. |
Co-authored-by: Blake R <[email protected]>
Feature description
Currently chats are listed oldest first (highest) in
ragna ui
. It seems more helpful more most use cases to reverse that order and have newer chats appear higher in the chat list in the side bar of ragna ui.Value and/or benefit
Better UX
Anything else?
No response
The text was updated successfully, but these errors were encountered: