⚡ Bolt: Optimize unresolved files sorting performance#48
Conversation
…zian transform Co-authored-by: jspann21 <179991454+jspann21@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: Refactored the
sortedItemsuseMemoblock inUnresolvedFilesSection.tsxto use the Schwartzian transform (decorate-sort-undecorate).🎯 Why: The custom sort comparison function was repeatedly calling$O(N \log N)$ times during UI re-renders, causing potential main-thread lag for large paginated sets.
sanitizeDisplayTextandfileExt, meaning expensive operations (like evaluating 3 regexes per string) were executed📊 Impact: Reduces$O(N \log N)$ back down to exactly $O(N)$ , mitigating a hidden React rendering bottleneck.
sanitizeDisplayTextstring manipulation evaluations from🔬 Measurement: Local tests and linting check out fine. The pre-computation ensures strings are sanitized exactly once per component lifecycle per item instead of during every single V8 comparison iteration.
PR created automatically by Jules for task 13962468906903597703 started by @jspann21