⚡ Bolt: optimize scroll-to-top listener state dispatches - #122
⚡ Bolt: optimize scroll-to-top listener state dispatches#122google-labs-jules[bot] wants to merge 1 commit into
Conversation
|
👋 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.
|
💡 What: Optimized
ScrollToTopButtonscroll event listener insrc/components/upArrow.tsx.🎯 Why: During user scrolling, the
scrollevent fires dozens of times per second. Previously, callingsetIsVisible(window.scrollY > 300)on every scroll event caused React state dispatches even when the boolean visibility state didn't change.📊 Impact: Caching the visibility state in a local closure variable (
isCurrentlyVisible) prevents redundantsetStatecalls and React scheduler dispatches on every scroll tick, eliminating unnecessary work on the main thread during scrolling.🔬 Measurement: Verified with unit tests (
pnpm test) and type checking (pnpm exec tsc --noEmit).PR created automatically by Jules for task 15504515988094757589 started by @amrabed