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
I keep losing threads in the sidebar because active threads sort by creation time, so the thread I worked on five minutes ago can sit below ones from yesterday. I get why V2 keeps rows stable (#8231 makes a good case against reshuffling on every message), but for my workflow recency matters more than stability.
There's already a sidebarThreadSortOrder setting that defaults to updated_at and V2 just ignores it. Would you take a PR that wires that existing setting through Sidebar V2 as an opt-in, keeping the current stable order as the default? Happy to build it if the direction sounds right.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I keep losing threads in the sidebar because active threads sort by creation time, so the thread I worked on five minutes ago can sit below ones from yesterday. I get why V2 keeps rows stable (#8231 makes a good case against reshuffling on every message), but for my workflow recency matters more than stability.
There's already a
sidebarThreadSortOrdersetting that defaults toupdated_atand V2 just ignores it. Would you take a PR that wires that existing setting through Sidebar V2 as an opt-in, keeping the current stable order as the default? Happy to build it if the direction sounds right.All reactions