fix(bug): clear resumes on logout to prevent seeing resumes from previously logged in accounts

[MagicalGlove]

Clear Resumes on logout

Changes

When logging out, the queryData from the key "resumes" is set to null

Why

When a user logs out, the resumes aren't cleared. If you then create a new account, the resumes from the previously logged in account are visible.
Trying to interact with resumes from a previously logged in account returns errors, preventing it from being a serious bug, but clearing them is, in my opinion, still the best approach.

Summary by CodeRabbit

• Bug Fixes
  • Improved logout behavior to ensure that associated personal data is cleared reliably after logout, whether successful or encountering an error, resulting in a more consistent and secure experience.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes enhance the logout functionality in the client application by modifying the useLogout hook in the logout.ts file. The handling of query data in the onSuccess and onError callbacks of the useMutation hook has been updated. The hardcoded array ["user"] has been replaced with the constant USER_KEY, and both callbacks now include a new line to set the query data for RESUMES_KEY to null, ensuring that both user and resumes data are reset upon logout.

Changes

File Path	Change Summary
apps/client/src/services/auth/logout.ts	Updated useLogout hook to replace ["user"] with USER_KEY in onSuccess and onError callbacks, and added queryClient.setQueryData(RESUMES_KEY, null); in both callbacks.

Sequence Diagram(s)

sequenceDiagram
    participant UI as UI Component
    participant Logout as useLogout Hook
    participant QC as QueryClient

    UI->>Logout: Initiate logout process
    alt Logout successful
        Logout->>QC: setQueryData(USER_KEY, null)
        Logout->>QC: setQueryData(RESUMES_KEY, null)
    else Logout error
        Logout->>QC: setQueryData(USER_KEY, null)
        Logout->>QC: setQueryData(RESUMES_KEY, null)
    end

Loading

Poem

In the code forest I hop along,
Clearing old data where it didn't belong.
On logout success or error in sight,
Resumes reset, keeping data light.
A rabbit cheers with delight! 🐇

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 76bbe7d and 249104e.

📒 Files selected for processing (1)

• apps/client/src/services/auth/logout.ts (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• apps/client/src/services/auth/logout.ts

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.