Skip to content

Comments

fix: the issue of compose new mail while on draft folder#1240

Merged
MrgSub merged 2 commits intoMail-0:stagingfrom
abhix4:fix/persistent-draftId
Jun 7, 2025
Merged

fix: the issue of compose new mail while on draft folder#1240
MrgSub merged 2 commits intoMail-0:stagingfrom
abhix4:fix/persistent-draftId

Conversation

@abhix4
Copy link
Contributor

@abhix4 abhix4 commented Jun 7, 2025

Description

currently if you try to compose new mail while staying in drafts folder (try after opening a draft mail), you will get the drafted mail prefilled .

fix: #1238

Type of Change

Please delete options that are not relevant.

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature with breaking changes)
  • 📝 Documentation update
  • 🎨 UI/UX improvement
  • 🔒 Security enhancement
  • ⚡ Performance improvement

Areas Affected

Please check all that apply:

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

Testing Done

Describe the tests you've 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

For changes involving data or authentication:

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

Checklist

  • I have read the CONTRIBUTING document
  • My code follows the project's style guidelines
  • I have performed a self-review of my code
  • I have commented my code, particularly in complex areas
  • I have updated the documentation
  • 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.

Summary by CodeRabbit

  • Bug Fixes
    • Closing the compose email dialog now properly clears any associated draft, ensuring drafts are no longer linked after the dialog is closed.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 7, 2025

Walkthrough

The change updates the email compose dialog logic to reset the draft ID by setting it to null whenever the dialog is closed. This ensures that any association with a previous draft is cleared, preventing unintended persistence of draft state when composing a new email.

Changes

File(s) Change Summary
apps/mail/components/create/create-email.tsx Added setDraftId(null) to handleDialogClose to clear draft state.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant ComposeDialog
    participant StateManager

    User->>ComposeDialog: Close compose dialog
    ComposeDialog->>StateManager: set isComposeOpen = false
    ComposeDialog->>StateManager: setDraftId(null)
    StateManager-->>ComposeDialog: Draft state cleared
Loading

Assessment against linked issues

Objective Addressed Explanation
Ensure composing a new mail does not prefill with previous draft state (#1238)

Assessment against linked issues: Out-of-scope changes

No out-of-scope changes found.

Possibly related PRs

  • Fix Drafts dissappearing on save #1203: Both PRs modify the handling of the draftId state related to email composition, with the main PR adding a reset of draftId on dialog close and the retrieved PR streamlining draftId state management via useQueryState and removing redundant synchronization logic.

Suggested reviewers

  • ahmetskilinc
  • MrgSub

Poem

Compose anew, let drafts be gone,
With every close, the slate is drawn.
No ghostly words from mails before,
Just empty space—compose once more!
🐇✉️
Hopping forward, bugs now few,
The inbox fresh, and so are you!


📜 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 48aa827 and ff2fe19.

📒 Files selected for processing (1)
  • apps/mail/components/create/create-email.tsx (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • apps/mail/components/create/create-email.tsx
✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 01867f0 and 48aa827.

📒 Files selected for processing (1)
  • apps/mail/components/create/create-email.tsx (1 hunks)
🔇 Additional comments (1)
apps/mail/components/create/create-email.tsx (1)

158-158: The fix correctly addresses the stated bug.

While the implementation could be more targeted, this change does solve the core issue described in the PR objectives. Clearing the draft ID ensures that when users compose new emails after viewing drafts, they get a clean compose window instead of prefilled draft content.

@MrgSub MrgSub merged commit c93ee3c into Mail-0:staging Jun 7, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[bug]: draft mail state persists when tried to compose new mail

2 participants