Fix: sorted thread not stable

[samhvw8]

Describe Your Changes

• This code block make when fetching threads data updated again to the backend, that leads to all threads have the same updated field

Fixes Issues

• Closes Chats sorting is not stable #5334

Self Checklist

• Added relevant comments, esp in complex areas
• Updated docs (for bug fixes / features)
• Created issues for follow-up changes or refactoring needed

---

Important

Removes redundant updateThread call in setThreads in useThreads.ts to fix unstable thread sorting.

• Behavior:
  • Removes redundant updateThread call in setThreads in useThreads.ts, preventing all threads from having the same updated field.
• Fixes:
  • Closes issue Chats sorting is not stable #5334 regarding unstable thread sorting.

^{This description was created by for e1495fc. You can customize this summary. It will automatically update as commits are pushed.}

[louis-menlo]

LGTM

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to e1495fc in 52 seconds. Click for details.

• Reviewed 16 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 1 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. web-app/src/hooks/useThreads.ts:34

• Draft comment:
  Removing the redundant updateThread loop in setThreads prevents unnecessary backend updates that reset thread timestamps, thereby stabilizing the thread order. This fix appears to resolve issue #5334.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, explaining the effect of a change and mentioning an issue it resolves. It doesn't ask for any specific action or suggest any improvements.

Workflow ID: wflow_SfVqkqNXh2nCxbul

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}