⚡ Bolt: Optimize FolderView rendering stability #72
Conversation
- Decoupled `FolderView` skeleton state from global `foldersLoading` context. - Prevents unnecessary full-page skeleton flash when the folder list refreshes in the background while emails are already loaded. - Improved perceived performance and UX stability. - Cleaned up unused variables.
|
👋 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: Decoupled the
FolderViewloading state from the globalfoldersLoadingcontext provided byLayout.🎯 Why: The previous logic caused the entire email list to unmount and show skeletons whenever
fetchFolderswas triggered in the parent layout (e.g., during periodic refreshes or after actions), even if the email list data was already present. This resulted in a disruptive flashing effect.📊 Impact: Eliminates redundant re-renders of the skeleton state during folder refreshes. The email list now remains stable and visible while the sidebar updates in the background.
🔬 Measurement: Verified via logic simulation and visual code analysis that the skeleton is now only triggered by the local
loadingstate (email fetch), preventing the flash.PR created automatically by Jules for task 13131381826196355293 started by @Mr-Dark-debug