⚡ Bolt: Concurrent email sending via Promise.all and next/link optimization - #93
⚡ Bolt: Concurrent email sending via Promise.all and next/link optimization#93Snigdh41 wants to merge 1 commit into
Conversation
…Promise.all Co-authored-by: Snigdh41 <43762408+Snigdh41@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: Executed independent
resend.emails.sendAPI calls concurrently usingPromise.all(). Also optimized the Navbar logo link to use Next.js's<Link>instead of an<a>tag to prevent full page reloads.🎯 Why: The notification email and auto-reply email were being sent sequentially, meaning the total time taken was the sum of both requests. Since they are independent, they can run concurrently. Using
<Link>for navigation prevents full page reloads and provides a smoother user experience in Next.js apps.📊 Impact: Reduces the total latency of the contact API endpoint by executing external email requests in parallel, significantly improving the response time for users. Using
<Link>improves client-side routing speed.🔬 Measurement: Verify the contact API endpoint responds faster when sending emails. Click the home logo link to ensure it navigates client-side without a full page reload.
PR created automatically by Jules for task 15908048257460050106 started by @Snigdh41