Skip to content

Comments

fixes issues with selected email optimistic updates#1146

Merged
BlankParticle merged 1 commit intostagingfrom
optimistic-updates-update
May 29, 2025
Merged

fixes issues with selected email optimistic updates#1146
BlankParticle merged 1 commit intostagingfrom
optimistic-updates-update

Conversation

@ahmetskilinc
Copy link
Contributor

@ahmetskilinc ahmetskilinc commented May 29, 2025

TL;DR

Improved mail list hotkey functionality by adding a shouldUseHover flag to determine when to use hover actions versus bulk selection actions.

What changed?

  • Added a shouldUseHover flag that checks if bulk selection is empty
  • Updated hotkey handlers (markAsRead, markAsUnread, archiveEmail) to use this flag when determining whether to act on hovered email or selected emails
  • Removed unused imports and functions:
    • Removed useQueryClient, useTRPC, useStats imports
    • Removed refetch, mutateStats, invalidateCount functions
    • Removed a console.log statement in the selectAll function
  • Updated dependency arrays in useCallback hooks to include the new shouldUseHover flag

How to test?

  1. Test mail list hotkeys with no emails selected:

    • Hover over an email and use keyboard shortcuts to mark as read/unread or archive
    • Verify actions apply only to the hovered email
  2. Test mail list hotkeys with emails selected:

    • Select multiple emails and use keyboard shortcuts
    • Verify actions apply to all selected emails regardless of hover state

Why make this change?

This change improves the user experience by making the hotkey behavior more predictable and intuitive. When users have explicitly selected emails, actions should apply to those selections. When no emails are selected, actions should apply to the currently hovered email. This creates a more consistent interaction model and prevents accidental operations on unintended emails.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 29, 2025

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


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 29, 2025 18:17
@BlankParticle BlankParticle merged commit efb2f59 into staging May 29, 2025
3 checks passed
Copy link
Contributor

Merge activity

@BlankParticle BlankParticle deleted the optimistic-updates-update branch May 29, 2025 18:18
MrgSub pushed a commit that referenced this pull request May 29, 2025
Improved mail list hotkey functionality by adding a `shouldUseHover` flag to determine when to use hover actions versus bulk selection actions.

- Added a `shouldUseHover` flag that checks if bulk selection is empty
- Updated hotkey handlers (markAsRead, markAsUnread, archiveEmail) to use this flag when determining whether to act on hovered email or selected emails
- Removed unused imports and functions:
  - Removed `useQueryClient`, `useTRPC`, `useStats` imports
  - Removed `refetch`, `mutateStats`, `invalidateCount` functions
  - Removed a console.log statement in the selectAll function
- Updated dependency arrays in useCallback hooks to include the new `shouldUseHover` flag

1. Test mail list hotkeys with no emails selected:
   - Hover over an email and use keyboard shortcuts to mark as read/unread or archive
   - Verify actions apply only to the hovered email

2. Test mail list hotkeys with emails selected:
   - Select multiple emails and use keyboard shortcuts
   - Verify actions apply to all selected emails regardless of hover state

This change improves the user experience by making the hotkey behavior more predictable and intuitive. When users have explicitly selected emails, actions should apply to those selections. When no emails are selected, actions should apply to the currently hovered email. This creates a more consistent interaction model and prevents accidental operations on unintended emails.
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