⚡ Bolt: Optimize Zustand record filtering in stores#2220
⚡ Bolt: Optimize Zustand record filtering in stores#2220
Conversation
Co-authored-by: georgi <19498+georgi@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. |
Co-authored-by: georgi <19498+georgi@users.noreply.github.com>
Co-authored-by: georgi <19498+georgi@users.noreply.github.com>
Co-authored-by: georgi <19498+georgi@users.noreply.github.com>
Co-authored-by: georgi <19498+georgi@users.noreply.github.com>
This PR implements a performance optimization focused on reducing intermediate array allocations in critical Zustand stores (
ErrorStore,ExecutionTimeStore,VibeCodingStore).What:
Replaced
Object.fromEntries(Object.entries(record).filter(...))patterns with optimizedfor...inloops and shallow-copy-and-delete operations.Why:
The previous pattern allocates intermediate arrays during
Object.entries()which negatively impacts garbage collection and overall main thread execution time, particularly during rapid dictionary updates and workflow resets.Impact:
Improves execution and cleanup responsiveness during store operations.
Also updated
ZUSTAND_BEST_PRACTICES.mdso that future developers will adhere to this more performant pattern. Tests and linters passing.PR created automatically by Jules for task 8479677575715052144 started by @georgi