fix: email visibility issue when moving between folders

[gitstart-opensource]

Description

• closes #890
• When moving an email from one folder to another, the email wasn't immediately visible in the destination folder without a page refresh.
  • This was because React Query's default invalidation only triggers refetches for "active" queries, and the destination folder's query wasn't active at the time of invalidation.
• This PR modifies the useMoveTo hook to invalidate the query for the destination folder after a move operation, ensuring that when a user navigates to the destination folder, the query is marked as stale and will be automatically refetched, making the moved email immediately visible without requiring a page refresh.

---

Type of Change

• [x] 🐛 Bug fix (non-breaking change which fixes an issue)

Areas Affected

• [ ] Email Integration (Gmail, IMAP, etc.)
• [x] User Interface/Experience
• [ ] Authentication/Authorization
• [ ] Data Storage/Management
• [ ] API Endpoints
• [ ] Documentation
• [ ] Testing Infrastructure
• [ ] Development Workflow
• [ ] Deployment/Infrastructure

Testing Done

• [ ] Unit tests added/updated
• [ ] Integration tests added/updated
• [ ] Manual testing performed
• [ ] Cross-browser testing (if UI changes)
• [ ] Mobile responsiveness verified (if UI changes)

Security Considerations

N/A

• [ ] No sensitive data is exposed
• [ ] Authentication checks are in place
• [ ] Input validation is implemented
• [ ] Rate limiting is considered (if applicable)

Checklist

• [x] I have read the CONTRIBUTING document
• [x] My code follows the project's style guidelines
• [x] I have performed a self-review of my code
• [ ] I have commented my code, particularly in complex areas
• [ ] I have updated the documentation
• [x] My changes generate no new warnings
• [ ] I have added tests that prove my fix/feature works
• [ ] All tests pass locally
• [ ] Any dependent changes are merged and published

---

By submitting this pull request, I confirm that my contribution is made under the terms of the project's license.

[vercel[bot]]

@gitstart is attempting to deploy a commit to the Zero Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai[bot]]

[!IMPORTANT]

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in 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.

[MrgSub]

Please use the new syntax

queryClient.invalidateQueries({
                queryKey: trpc.mail.get.queryKey({ id: message.id }),
              }),

[MrgSub]

You need to invalidate using the folder parameter @gitstart-opensource