⚡ Bolt: Prevent redundant auto-save processing via memoized resume data

[aafre]

💡 What: Wrapped the inline resumeData object passed from useSaveIntegration.ts to useCloudSave with a useMemo block.

🎯 Why: Passing an inline object literal caused it to be a new reference on every single render of the useSaveIntegration hook. This in turn forced the useEffect block inside useCloudSave to continuously track a "changed" dependency and unnecessarily execute JSON.stringify on the entire resume on every component render, even when the data itself had not mutated.

📊 Impact: Reduces CPU blocking by eliminating redundant O(N) serialization sweeps inside the auto-save loop, creating a much smoother typing and interaction experience for the user on large resumes.

🔬 Measurement: Verify via React Profiler that internal effects in useCloudSave now only run when the actual deep properties change, avoiding rapid re-evaluations during unrelated re-renders (like user idle updates or polling).

---

PR created automatically by Jules for task 340806267519828884 started by @aafre

[google-labs-jules]

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly improves the performance of the auto-save feature by addressing a common React optimization pitfall. By ensuring that the resumeData object maintains a stable reference across renders, it eliminates redundant serialization and processing, resulting in a more responsive and fluid user experience, especially when interacting with large resumes.

Highlights

• Performance Optimization: Implemented useMemo for the resumeData object passed to useCloudSave to prevent unnecessary re-renders and expensive JSON.stringify operations, which previously occurred due to new object references on every render.
• Developer Best Practices: Added a new learning document (.jules/bolt.md) to highlight the importance of memoizing object parameters when passing them to custom hooks that perform deep dependency tracking.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly identifies and fixes a performance issue by memoizing the resumeData object passed to the useCloudSave hook. This prevents unnecessary re-renders and expensive serialization operations. The change is well-implemented. I have one suggestion to further improve the memoization strategy for the fallback case to make it more robust.

[gemini-code-assist]

While this useMemo is a great performance improvement, the fallback object is a new literal. This means if contactInfo or templateId is falsy, any change in other dependencies (like sections) will create a new fallback object reference. This triggers an unnecessary effect run in useCloudSave (though it bails out early as enabled is false).

To make this fully robust, the fallback object should have a stable reference. The best approach is to define it as a constant outside the useSaveIntegration hook.

Example:

const EMPTY_RESUME_DATA = { contact_info: { name: '', location: '', email: '', phone: '' }, sections: [], template_id: '' };

export const useSaveIntegration = ({ ... }) => {
  // ...
  const memoizedResumeData = useMemo(() => {
    return contactInfo && templateId
      ? {
          contact_info: contactInfo,
          sections: sections,
          template_id: templateId,
        }
      : EMPTY_RESUME_DATA;
  }, [contactInfo, sections, templateId]);
  // ...
}

This ensures the empty data object reference is always stable, preventing the downstream effect from running unnecessarily.

References

1. The dependency array of useMemo should include the values that the memoized calculation depends on. Ensuring stable references for memoized values, including fallback objects, is crucial to prevent unnecessary re-renders and downstream effects, aligning with the principle of effective useMemo usage.

[aafre]

Closing: superseded by #404 (better variable naming). Cherry-picked into #457.

[google-labs-jules]

Closing: superseded by #404 (better variable naming). Cherry-picked into #457.

Understood. Acknowledging that this work is superseded and stopping work on this task.