⚡ Bolt: Optimize CoffeeBatch list rendering - #62
Conversation
…des and memoizing hidden elements. Co-authored-by: AntonioCardenas <11583391+AntonioCardenas@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. |
✅ Deploy Preview for heartfelt-swan-19c038 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
💡 What
Optimized the rendering of
BatchItemin the paginated CoffeeBatch list. Wrapped the item inReact.memowith a custom comparison function that bypasses re-rendering for items that remain hidden on another page. Additionally, deferred rendering the heavy<QRCode>element (which generates SVGs/Canvas elements) until the item is visible on the current page.🎯 Why
The application uses
ReactHTMLTableToExcelfor exports, which forces all paginated items to remain in the DOM structure (via ahideCSS class). When switching pages, all hundreds or thousands of these hidden elements were undergoing React reconciliation, and rendering the expensive<QRCode>components needlessly. This caused extreme layout thrashing and sluggish pagination.📊 Impact
🔬 Measurement
PR created automatically by Jules for task 15990994295160388837 started by @AntonioCardenas