⚡ Bolt: [performance improvement] Batched artifact fetching in board hooks#51
Conversation
…hooks Co-authored-by: Donach <39565367+Donach@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. |
💡 What: Added
findManyByIdstoArtifactRepositoryusing a batchedinArrayquery instead of querying each artifact individually inside the FeathersJS hook loops, and refactored the hooks to create an intermediate artifact mapping.🎯 Why: FeathersJS board hooks evaluate nested
board.objectsrelationships. Previously, when multiple objects pointed to an artifact, each lookup triggered a separatefindByIdresulting in an N+1 query issue.📊 Impact: Considerably reduces database roundtrips during any multi-object board payload resolution. Lookups are condensed into one batched database operation.
🔬 Measurement: Verify by executing board hook queries with multiple internal artifact references. Test suites continue to pass correctly, reflecting the preservation of functionality with improved performance.
PR created automatically by Jules for task 2747807462789992934 started by @Donach