⚡ Bolt: Optimize DocumentsTable sorting#65
Conversation
Wrapped the `sortedRows` calculation in `useMemo` to prevent expensive sorting operations (O(N log N)) on every render. This specifically improves performance when toggling group expansion, which updates local state but should not require re-sorting the data. Verified with new unit tests and full test suite. Co-authored-by: kourdroid <36898160+kourdroid@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. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
1 participant
💡 What: Memoized the
sortedRowscalculation insrc/components/documents-table.tsxusinguseMemo.🎯 Why: The table was re-sorting the entire dataset on every render, including when interacting with local state like expanding/collapsing groups. This is inefficient, especially as the dataset grows.
📊 Impact: Reduces the computational overhead of re-renders. Sorting is now only performed when
documentRows,sortField, orsortDirectionchanges.🔬 Measurement: Verified with
src/__tests__/documents-table.test.tsxand manual frontend verification (screenshot).PR created automatically by Jules for task 3676249876538674905 started by @kourdroid