⚡ Bolt: Pre-calculate derived search properties for faster filtering#71
⚡ Bolt: Pre-calculate derived search properties for faster filtering#71MrAlokTech wants to merge 1 commit intomainfrom
Conversation
Co-authored-by: MrAlokTech <107493955+MrAlokTech@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. |
Deploying classnotes with
|
| Latest commit: |
d1c3cc4
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://6367014d.classnotes.pages.dev |
| Branch Preview URL: | https://bolt-pre-index-search-129013.classnotes.pages.dev |
💡 What: Created a
prepareSearchIndexfunction that pre-calculates_searchStr,_isNew, and_formattedDateonce per data load (from network or cache). Optimized therenderPDFsfilter loop to use this pre-calculated string and early returns, preventing repeated date parsing, string concatenation, and lowercasing on every search keystroke.🎯 Why: Searching and filtering happens constantly on the frontend. Calculating complex strings and Date math inside a
.filterarray iteration block for every keystroke creates CPU spikes and slows down the UI, especially for larger arrays.📊 Impact: Shifts O(N*M) continuous UI blocking calculations (where N is PDFs and M is keystrokes) to a single O(N) calculation on load. Drastically reduces time spent in the main thread during typing/searching.
🔬 Measurement: Verify by typing rapidly in the search bar. The delay before rendering should be noticeably smoother, and JS profiler will show significantly less time spent inside
renderPDFsandcreatePDFCard.PR created automatically by Jules for task 12901333783784945901 started by @MrAlokTech