Skip to content

Comments

fixes some optimistic action bugs#1171

Merged
ahmetskilinc merged 5 commits intostagingfrom
05-31-fixes_some_optimistic_action_bugs
May 31, 2025
Merged

fixes some optimistic action bugs#1171
ahmetskilinc merged 5 commits intostagingfrom
05-31-fixes_some_optimistic_action_bugs

Conversation

@ahmetskilinc
Copy link
Contributor

@ahmetskilinc ahmetskilinc commented May 31, 2025

TL;DR

Added redirect for missing folder parameter and fixed query invalidation for mail threads.

What changed?

  • Imported Navigate component from 'react-router'
  • Added a redirect in the loader function when the folder parameter is missing, sending users to the inbox
  • Fixed query invalidation in the optimistic actions hook by changing queryKey to infiniteQueryKey for the listThreads query

How to test?

  1. Navigate to a URL without a folder parameter (e.g., /mail/) and verify it redirects to /mail/inbox
  2. Perform actions that trigger optimistic updates (like moving threads between folders) and verify that the thread lists update correctly

Why make this change?

The redirect ensures users always land on a valid mail folder page even if they access an incomplete URL. The query invalidation fix ensures that the UI properly refreshes after optimistic actions are performed, maintaining data consistency between the client and server.

Summary by CodeRabbit

  • Bug Fixes

    • Improved folder navigation by redirecting to the inbox if the folder parameter is missing.
  • Refactor

    • Optimized the handling of optimistic actions for mail operations, triggering actions via toast lifecycle events instead of timeouts.
    • Enhanced memoization logic for thread lists to update more precisely based on data changes.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 31, 2025

Walkthrough

The updates modify the mail application's folder page loader to redirect to the inbox if the folder parameter is missing, refactor the optimistic actions hook to use toast lifecycle callbacks instead of timeouts for deferred execution, and adjust the memoization dependencies in the threads hook for more precise recalculation based on query updates.

Changes

File(s) Change Summary
apps/mail/app/(routes)/mail/[folder]/page.tsx Added import of Navigate; loader redirects early to inbox if folder param missing before session check.
apps/mail/hooks/use-optimistic-actions.ts Removed timeout-based action execution; use toast lifecycle callbacks for triggering actions; updated queue logic.
apps/mail/hooks/use-threads.ts Modified useMemo dependencies to use threadsQuery.dataUpdatedAt instead of session; memo logic unchanged.

Possibly related PRs

Poem

In the burrows of code, a redirect appears,
To the inbox you’ll go if no folder is here.
Optimistic actions now hop with toast’s close,
No more ticking clocks, as the background queue grows.
Threads now refresh with a timelier cheer—
A rabbit’s delight as the mailbox runs clear! 🐇📬


📜 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 5cca0ab and 5f8946e.

📒 Files selected for processing (1)
  • apps/mail/hooks/use-optimistic-actions.ts (4 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • apps/mail/hooks/use-optimistic-actions.ts
✨ 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 Author

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

@ahmetskilinc ahmetskilinc marked this pull request as ready for review May 31, 2025 16:28
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: 0

🧹 Nitpick comments (5)
apps/mail/hooks/use-threads.ts (1)

38-45: Remove unused dependency from useMemo.

The backgroundQueue variable is included in the dependency array but is not used within the useMemo callback. This causes unnecessary recalculations of the threads array whenever the background queue changes.

  const threads = useMemo(() => {
    return threadsQuery.data
      ? threadsQuery.data.pages
          .flatMap((e) => e.threads)
          .filter(Boolean)
          .filter((e) => !isInQueue(`thread:${e.id}`))
      : [];
-  }, [threadsQuery.data, threadsQuery.dataUpdatedAt, isInQueue, backgroundQueue]);
+  }, [threadsQuery.data, threadsQuery.dataUpdatedAt, isInQueue]);
apps/mail/app/(routes)/mail/[folder]/page.tsx (1)

1-1: Remove unused import.

The Navigate component is imported but never used in this file. Only useNavigate is used on line 25.

-import { Navigate, useLoaderData, useNavigate } from 'react-router';
+import { useLoaderData, useNavigate } from 'react-router';
apps/mail/hooks/use-optimistic-actions.ts (3)

142-149: Remove console.log statements from production code.

Debug console.log statements should not be included in production code.

  toast(bulkActionMessage, {
    onAutoClose: () => {
-      console.log('auto closed');
      doAction();
    },
    onDismiss: () => {
-      console.log('dismissed');
      doAction();
    },

141-158: Consider setting explicit toast duration.

The toast no longer has an explicit duration set, which might lead to inconsistent behavior across different environments or toast configurations.

  toast(bulkActionMessage, {
+    duration: UNDO_DELAY,
    onAutoClose: () => {

298-306: Extract duplicated background queue cleanup logic.

The background queue deletion logic is duplicated across multiple execute and undo callbacks. Consider extracting this into a helper function.

+  const cleanupBackgroundQueue = useCallback((threadIds: string[]) => {
+    threadIds.forEach((id) => {
+      setBackgroundQueue({ type: 'delete', threadId: `thread:${id}` });
+    });
+  }, [setBackgroundQueue]);

  // Then in the execute and undo callbacks:
-          threadIds.forEach((id) => {
-            setBackgroundQueue({ type: 'delete', threadId: `thread:${id}` });
-          });
+          cleanupBackgroundQueue(threadIds);

Also applies to: 354-363

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2eac4f3 and 5cca0ab.

📒 Files selected for processing (3)
  • apps/mail/app/(routes)/mail/[folder]/page.tsx (2 hunks)
  • apps/mail/hooks/use-optimistic-actions.ts (5 hunks)
  • apps/mail/hooks/use-threads.ts (1 hunks)
🔇 Additional comments (2)
apps/mail/app/(routes)/mail/[folder]/page.tsx (1)

13-14: Good defensive programming!

The early redirect ensures users always land on a valid folder page, preventing potential errors from missing folder parameters.

apps/mail/hooks/use-optimistic-actions.ts (1)

55-57: Correct usage of infiniteQueryKey for infinite queries.

Good fix! Using infiniteQueryKey instead of queryKey for the listThreads query ensures proper invalidation of infinite query data.

@ahmetskilinc ahmetskilinc merged commit 2825f8a into staging May 31, 2025
3 checks passed
Copy link
Contributor Author

Merge activity

@ahmetskilinc ahmetskilinc deleted the 05-31-fixes_some_optimistic_action_bugs branch May 31, 2025 16:31
@coderabbitai coderabbitai bot mentioned this pull request Jun 5, 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