Skip to content

Comments

Prefetch latest html content#1620

Merged
MrgSub merged 1 commit intostagingfrom
07-03-prefetch_latest_html_content
Jul 4, 2025
Merged

Prefetch latest html content#1620
MrgSub merged 1 commit intostagingfrom
07-03-prefetch_latest_html_content

Conversation

@MrgSub
Copy link
Collaborator

@MrgSub MrgSub commented Jul 4, 2025

READ CAREFULLY THEN REMOVE

Remove bullet points that are not relevant.

PLEASE REFRAIN FROM USING AI TO WRITE YOUR CODE AND PR DESCRIPTION. IF YOU DO USE AI TO WRITE YOUR CODE PLEASE PROVIDE A DESCRIPTION AND REVIEW IT CAREFULLY. MAKE SURE YOU UNDERSTAND THE CODE YOU ARE SUBMITTING USING AI.

  • Pull requests that do not follow these guidelines will be closed without review or comment.
  • If you use AI to write your PR description your pr will be close without review or comment.
  • If you are unsure about anything, feel free to ask for clarification.

Description

Please provide a clear description of your changes.


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

Add screenshots or recordings here if applicable.


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

    • Improved email content loading by prefetching and caching processed email content, ensuring faster and smoother viewing, especially when switching between messages.
    • Enhanced handling of trusted senders and theme settings for displaying external images in emails.
  • Bug Fixes

    • Improved reliability when displaying processed email content and detecting blocked images.
  • Performance

    • Optimized email rendering by proactively caching processed content based on sender trust and theme.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 4, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

The changes refactor how processed email content and its metadata are handled in the MailContent component, separating data fetching from side-effect state updates. In the useThread hook, the code introduces proactive prefetching and caching of processed email content based on sender trust and theme, replacing session-based logic with settings and theme hooks.

Changes

File(s) Change Summary
apps/mail/components/mail/mail-content.tsx Refactored to return processed HTML and image-blocked flag as an object; moved side-effect state updates to a useEffect; updated rendering to use new data structure.
apps/mail/hooks/use-threads.ts Introduced settings and theme hooks; added logic to determine trusted senders; implemented prefetch and caching of processed email content keyed by message, trust, and theme.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant MailContent
    participant useThread
    participant processEmailContent

    User->>MailContent: Render email view
    MailContent->>useThread: Fetch thread data
    useThread->>processEmailContent: Prefetch processed content (based on trust & theme)
    processEmailContent-->>useThread: Return { html, imagesBlocked }
    useThread-->>MailContent: Provide processed content
    MailContent->>MailContent: useEffect sets cspViolation if imagesBlocked
    MailContent->>User: Render processed HTML
Loading

Possibly related PRs

  • Mail-0/Zero#1584: Introduced the MailContent component, which is directly refined and extended by the current changes.

Poem

In the warren of code, a new thread appears,
Prefetching our mail with fewer delays and fears.
Trust and theme now guide what we show,
With images blocked, or allowed to flow.
A hop, a skip, for content so bright—
This rabbit ensures your inbox feels right!
🐇📬✨


📜 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 3fd7b97 and 25c1198.

📒 Files selected for processing (2)
  • apps/mail/components/mail/mail-content.tsx (2 hunks)
  • apps/mail/hooks/use-threads.ts (3 hunks)
✨ 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
Collaborator Author

MrgSub commented Jul 4, 2025

This stack of pull requests is managed by Graphite. Learn more about stacking.

@MrgSub MrgSub mentioned this pull request Jul 4, 2025
34 tasks
@MrgSub MrgSub marked this pull request as ready for review July 4, 2025 06:12
Copy link
Collaborator Author

MrgSub commented Jul 4, 2025

Merge activity

  • Jul 4, 6:12 AM UTC: A user started a stack merge that includes this pull request via Graphite.
  • Jul 4, 6:14 AM UTC: Graphite rebased this pull request as part of a merge.
  • Jul 4, 6:16 AM UTC: @MrgSub merged this pull request with Graphite.

@MrgSub MrgSub changed the base branch from 07-03-minor_fixes to graphite-base/1620 July 4, 2025 06:12
Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

PR Summary

Enhanced email content handling with prefetching optimization and improved security measures in the Mail-0/Zero email client.

  • Added smart prefetching in apps/mail/hooks/use-threads.ts to preprocess HTML content of latest messages using react-query's prefetchQuery
  • Improved security in apps/mail/components/mail/mail-content.tsx by separating CSP violation checks into a dedicated useEffect hook
  • Implemented theme-aware email content processing for better display consistency
  • Added trusted sender verification system for safer image loading
  • Optimized component state management by returning both processed HTML and image blocking status as a combined object

2 files reviewed, 2 comments
Edit PR Review Bot Settings | Greptile

Comment on lines +111 to +127
const prefetchEmailContent = async (message: ParsedMessage) => {
return queryClient.prefetchQuery({
queryKey: ['email-content', message.id, isTrustedSender, resolvedTheme],
queryFn: async () => {
const result = await processEmailContent({
html: message.decodedBody ?? '',
shouldLoadImages: isTrustedSender,
theme: (resolvedTheme as 'light' | 'dark') || 'light',
});

return {
html: result.processedHtml,
hasBlockedImages: result.hasBlockedImages,
};
},
});
};
Copy link
Contributor

Choose a reason for hiding this comment

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

style: prefetchEmailContent should use useCallback to avoid recreation on every render. Also consider adding error handling for failed prefetches

Comment on lines +129 to +132
useEffect(() => {
if (!threadQuery.data?.latest?.id) return;
prefetchEmailContent(threadQuery.data.latest);
}, [threadQuery.data?.latest]);
Copy link
Contributor

Choose a reason for hiding this comment

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

logic: useEffect dependency array missing prefetchEmailContent function. Add it to prevent stale closure issues

Suggested change
useEffect(() => {
if (!threadQuery.data?.latest?.id) return;
prefetchEmailContent(threadQuery.data.latest);
}, [threadQuery.data?.latest]);
useEffect(() => {
if (!threadQuery.data?.latest?.id) return;
prefetchEmailContent(threadQuery.data.latest);
}, [threadQuery.data?.latest, prefetchEmailContent]);

@MrgSub MrgSub changed the base branch from graphite-base/1620 to staging July 4, 2025 06:13
@MrgSub MrgSub force-pushed the 07-03-prefetch_latest_html_content branch from 525b9c9 to 25c1198 Compare July 4, 2025 06:14
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Bug: Prefetch Query Key Mismatch Causes Incomplete Caching

A query key mismatch exists between the prefetchEmailContent function in use-threads.ts and the actual email content query in mail-content.tsx. The prefetch uses isTrustedSender as the third element of the ['email-content', messageId, ..., resolvedTheme] query key, while the actual query uses isTrustedSender || temporaryImagesEnabled. This prevents prefetched data from being used when temporaryImagesEnabled is true but isTrustedSender is false, leading to unnecessary re-fetching and potentially incomplete cached content regarding image loading.

apps/mail/hooks/use-threads.ts#L111-L117

const prefetchEmailContent = async (message: ParsedMessage) => {
return queryClient.prefetchQuery({
queryKey: ['email-content', message.id, isTrustedSender, resolvedTheme],
queryFn: async () => {
const result = await processEmailContent({
html: message.decodedBody ?? '',
shouldLoadImages: isTrustedSender,

Fix in CursorFix in Web


Bug: Prefetch Hook Missing Dependencies

The useEffect responsible for prefetching email content has incomplete dependencies. It calls prefetchEmailContent, which captures isTrustedSender, resolvedTheme, processEmailContent, and queryClient. Since isTrustedSender and resolvedTheme are not included in the useEffect's dependency array, the prefetch will not re-run when these values change. This can lead to stale or incorrect data being prefetched and cached, as these values are crucial for the prefetch's queryKey and queryFn.

apps/mail/hooks/use-threads.ts#L128-L132

useEffect(() => {
if (!threadQuery.data?.latest?.id) return;
prefetchEmailContent(threadQuery.data.latest);
}, [threadQuery.data?.latest]);

Fix in CursorFix in Web


BugBot free trial expires on July 22, 2025
You have used $0.00 of your $50.00 spend limit so far. Manage your spend limit in the Cursor dashboard.

Was this report helpful? Give feedback by reacting with 👍 or 👎

@MrgSub MrgSub merged commit 007d845 into staging Jul 4, 2025
6 of 7 checks passed
@MrgSub MrgSub deleted the 07-03-prefetch_latest_html_content branch July 4, 2025 06:16
@coderabbitai coderabbitai bot mentioned this pull request Jul 4, 2025
34 tasks
@coderabbitai coderabbitai bot mentioned this pull request Jul 11, 2025
10 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.

1 participant