Skip to content

Comments

feat: Alert user when attachment keywords are present but no file is attached#1509

Merged
MrgSub merged 3 commits intoMail-0:stagingfrom
samrathreddy:feat/Attachments-validation-as-per-email-compose-body
Jun 27, 2025
Merged

feat: Alert user when attachment keywords are present but no file is attached#1509
MrgSub merged 3 commits intoMail-0:stagingfrom
samrathreddy:feat/Attachments-validation-as-per-email-compose-body

Conversation

@samrathreddy
Copy link
Contributor

@samrathreddy samrathreddy commented Jun 27, 2025

Description

Alerts the user if the email contains words like "attached" but no file is actually attached.


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

Additional Notes

Add any other context about the pull request here.

Screenshots/Recordings

Before:

Screen.Recording.2025-06-27.at.12.19.52.PM.mov

After:

Screen.Recording.2025-06-27.at.12.17.22.PM.mov

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

Summary by CodeRabbit

  • New Features
    • Added a warning when sending an email that mentions attachments but does not include any files. Users are prompted with a dialog to confirm if they want to send the email without attachments or recheck before sending.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 27, 2025

Walkthrough

A new feature was added to the email composer to detect if the email text references attachments but no files are attached. The send logic now checks for attachment-related keywords and, if found without any attachments, prompts the user with a warning dialog before allowing them to proceed or recheck.

Changes

File(s) Change Summary
apps/mail/components/create/email-composer.tsx Added detection for attachment keywords in email body, warning dialog, and split send logic into two functions.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant EmailComposer
    participant ModalDialog

    User->>EmailComposer: Click Send
    EmailComposer->>EmailComposer: Check for attachment keywords & attachments
    alt Keywords found & no attachments
        EmailComposer->>ModalDialog: Show attachment warning
        alt User chooses "Send Anyway"
            ModalDialog->>EmailComposer: Proceed with send
            EmailComposer->>EmailComposer: Send email
        else User chooses "Recheck"
            ModalDialog->>EmailComposer: Close warning, no send
        end
    else No keywords or attachments present
        EmailComposer->>EmailComposer: Send email
    end
Loading

Poem

A bunny with ears so tall and bright,
Checks for your files before taking flight.
"Did you mention a file, but none attached?"
A gentle warning, before your mail is dispatched.
Now emails hop safely, with nothing left behind,
Thanks to a composer that's thoughtful and kind!
🐇✉️


📜 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 20009df and f25f07b.

📒 Files selected for processing (1)
  • apps/mail/components/create/email-composer.tsx (5 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • apps/mail/components/create/email-composer.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

🧹 Nitpick comments (1)
apps/mail/components/create/email-composer.tsx (1)

158-165: Consider expanding keywords and optimizing placement.

The current keyword list covers common cases but could be more comprehensive. Consider adding keywords like "file attached", "attached file", "please find attached", etc.

Also, this array could be moved outside the component to avoid recreation on each render:

+const ATTACHMENT_KEYWORDS = [
+  'attachment',
+  'attached',
+  'attaching',
+  'see the file',
+  'see the files',
+  'file attached',
+  'attached file',
+  'please find attached',
+];

 export function EmailComposer({
   // ... props
 }: EmailComposerProps) {
-  const attachmentKeywords = [
-    'attachment',
-    'attached',
-    'attaching',
-    'see the file',
-    'see the files',
-  ];
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7956a36 and ce74b6f.

📒 Files selected for processing (1)
  • apps/mail/components/create/email-composer.tsx (5 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: danteissaias
PR: Mail-0/Zero#618
File: apps/mail/components/mail/mail-iframe.tsx:0-0
Timestamp: 2025-04-07T20:46:04.726Z
Learning: In the Zero mail application, the "Trust Sender" button for external images is only shown when a sender is not already in the trusted senders list (`settings?.trustedSenders`). This is controlled by the condition `!imagesEnabled && !settings?.externalImages`, where `imagesEnabled` is based on `isTrustedSender || settings?.externalImages` and `isTrustedSender` is determined by `settings?.trustedSenders?.includes(senderEmail)`. This design pattern prevents duplicate entries in the trusted senders list.
apps/mail/components/create/email-composer.tsx (3)
Learnt from: retrogtx
PR: Mail-0/Zero#1468
File: apps/server/src/trpc/routes/mail.ts:386-391
Timestamp: 2025-06-27T04:59:29.709Z
Learning: In apps/server/src/trpc/routes/mail.ts, the attachment processing logic conditionally handles mixed attachment types - it preserves existing File-like objects with arrayBuffer methods while only converting serialized attachments that need processing through toAttachmentFiles.
Learnt from: retrogtx
PR: Mail-0/Zero#1328
File: apps/mail/lib/hotkeys/mail-list-hotkeys.tsx:202-209
Timestamp: 2025-06-18T17:26:50.918Z
Learning: In apps/mail/lib/hotkeys/mail-list-hotkeys.tsx, the switchCategoryByIndex function using hardcoded indices for category hotkeys does not break when users reorder categories, contrary to the theoretical index-shifting issue. The actual implementation has constraints or mechanisms that prevent hotkey targeting issues.
Learnt from: danteissaias
PR: Mail-0/Zero#618
File: apps/mail/components/mail/mail-iframe.tsx:12-12
Timestamp: 2025-04-07T20:46:11.697Z
Learning: In the Mail-0/Zero application, sender emails are guaranteed to be non-empty when passed to components that handle them, making additional empty string validation unnecessary.
🧬 Code Graph Analysis (1)
apps/mail/components/create/email-composer.tsx (1)
apps/mail/components/ui/dialog.tsx (6)
  • Dialog (107-107)
  • DialogContent (112-112)
  • DialogHeader (113-113)
  • DialogTitle (115-115)
  • DialogDescription (116-116)
  • DialogFooter (114-114)
🔇 Additional comments (3)
apps/mail/components/create/email-composer.tsx (3)

134-134: LGTM: Clean state addition for dialog control.

The new state variable follows the existing pattern used by other dialogs in the component.


367-401: LGTM: Clean function refactoring maintains original behavior.

The rename from handleSend to proceedWithSend creates a clear separation of concerns while preserving all existing send logic intact.


1446-1474: LGTM: Well-implemented warning dialog with clear UX.

The dialog follows the existing component patterns and provides a clear user experience with appropriate action options. The button handlers correctly manage state and flow control.

@MrgSub MrgSub merged commit faa95f5 into Mail-0:staging Jun 27, 2025
3 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Jun 28, 2025
34 tasks
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.

2 participants