Refactor mailto handling and authentication check

[MrgSub]

Summary by CodeRabbit

• New Features
  • Enhanced the email composition experience by improving redirection. Users are now guided to sign in if authentication fails and redirected to a dedicated compose page when email link details are missing or invalid, ensuring a smoother, more intuitive draft creation process.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
0	🛑 Canceled (Inspect)			Apr 10, 2025 11:27pm

[coderabbitai]

Warning

Rate limit exceeded

@MrgSub has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 25 minutes and 17 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 3dfe231 and ca03974.

📒 Files selected for processing (1)

• apps/mail/app/(routes)/mail/compose/handle-mailto/route.ts (1 hunks)

Walkthrough

This pull request updates the GET function in the mailto route handler. It now verifies the user session using auth.api.getSession and redirects to the login page if the session is invalid. The function retrieves the mailto parameter from the URL, parsing it with parseMailtoUrl. If the parameter is missing or parsing fails, the user is redirected to the mail compose page. Additionally, the function attempts to create a draft via createDraftFromMailto, redirecting accordingly based on whether the draft creation is successful.

Changes

File Path	Summary of Changes
apps/mail/app/(routes)/mail/compose/handle-mailto/route.ts	Enhanced GET function by adding session validation (redirecting to login if invalid), mailto parameter retrieval with redirection if missing, URL parsing using parseMailtoUrl, and draft creation via createDraftFromMailto. The control flow now ensures proper redirection based on each step’s success or failure.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant R as GET Route Handler
    participant A as auth.api
    participant P as parseMailtoUrl
    participant D as createDraftFromMailto

    U->>R: Send GET request with mailto URL
    R->>A: getSession()
    A-->>R: Session validity result
    alt Invalid Session
        R->>U: Redirect to Login Page
    else Valid Session
        R->>R: Retrieve mailto parameter
        alt Parameter missing
            R->>U: Redirect to Mail Compose Page
        else Parameter present
            R->>P: parseMailtoUrl(mailto)
            P-->>R: Parsed result or failure
            alt Parse fails
                R->>U: Redirect to Mail Compose Page
            else Parse succeeds
                R->>D: createDraftFromMailto(parsedData)
                D-->>R: Draft result or failure
                alt Draft creation fails
                    R->>U: Redirect to Mail Compose Page
                else Draft created
                    R->>U: Redirect to Mail Compose Page with draft ID
                end
            end
        end
    end

Loading

Possibly related PRs

• feat: add mailto protocol handler support #574: This PR also revised the GET function in the same route to enhance mailto URL handling, including user redirection logic based on session and draft creation outcomes.

Poem

I’m a little rabbit, ready to code,
Hoping through pathways where redirections flow.
Session checks and drafts made in rhyme,
Parsing URLs one hop at a time.
Celebrate our changes—let's hop into a bright new design!

---

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.
  • 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 plan to trigger planning for file edits and PR creation.
• @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.