Repository navigation
Conversation
Memoize the \`rows\` and \`current\` states in \`useThreadList\` using \`useMemo\` to prevent expensive array filtering and sorting on every render, which is particularly beneficial during chat polling. Co-authored-by: bobdivx <6737167+bobdivx@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
💡 What: Added
useMemohooks for therowsandcurrentderived states inapps/web/src/components/chat/useThreadList.ts.🎯 Why:
useThreadListprocesses an array of agents to build nested hierarchies. Because chat polling triggers frequent re-renders, recalculating this array on every render caused unnecessary CPU overhead, especially when the lists become large.📊 Impact: Reduces unnecessary synchronous array
.filter(),.map(), and.sort()operations on every render during polling by memoizing the result until the underlying source data actually changes.🔬 Measurement: Verify tests still pass using
npm run testinapps/web. No visual changes should occur.PR created automatically by Jules for task 10345656599905561121 started by @bobdivx