Fix keyboard shortcuts while in input

[elie222]

Summary by CodeRabbit

• New Features
  • Enhanced email processing: Email tests, categorizations, and cold email validations now associate individual emails with a unique identifier. This improvement ensures more precise tracking and better overall email management.
  • Streamlined reply tracker: Keyboard navigation has been refined to support intuitive shortcuts for replying, resolving, and unresolving threads, providing a smoother and more efficient user experience.

[vercel]

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

Name	Status	Preview	Updated (UTC)
inbox-zero	🔄 Building (Inspect)	Visit Preview	Feb 9, 2025 1:18pm

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request updates multiple components by introducing a new property, messageId, into several data structures and function signatures. The changes span cold email handling, AI categorization, and keyboard navigation. In cold email flows, messageId is added to better track or process emails, replacing or supplementing threadId. The AI categorization logic is updated with a renaming (aicategorize to aiCategorize) and refined parameter passing. Additionally, the reply tracker now uses a new hook for keyboard navigation with specific key mappings, and a generic table keyboard navigation hook has been introduced.

Changes

Files	Change Summary
…/app/(app)/cold-email-blocker/TestRules.tsx …/utils/actions/cold-email.ts …/utils/actions/validation.ts …/utils/cold-email/is-cold-email.ts …/utils/gmail/message.ts	Added/modified messageId property across test email functions, validation schemas, and email processing functions, updating signatures to use messageId instead of threadId.
…/api/ai/categorize/controller.ts …/api/ai/categorize/validation.ts …/components/email-list/EmailList.tsx	Renamed aicategorize to aiCategorize; updated the categorize schema and email list actions to incorporate messageId along with refined threadId and date parameters.
…/app/(app)/reply-tracker/ReplyTrackerEmails.tsx	Replaced useTableKeyboardNavigation with useReplyTrackerKeyboardNav and revised keyboard handling to map 'r', 'd', and 'n' keys to reply, resolve, and unresolve actions.
…/hooks/useTableKeyboardNavigation.ts	Introduced a new custom hook that manages table keyboard navigation using arrow key events and an onKeyAction callback.

Sequence Diagram(s)

sequenceDiagram
  participant U as User
  participant RT as ReplyTrackerEmails
  participant KW as useReplyTrackerKeyboardNav
  participant AH as Action Handler

  U->>RT: Press key ('r', 'd', or 'n')
  RT->>KW: Forward key press event
  KW->>KW: Map key to corresponding action
  KW->>AH: Invoke onKeyAction callback
  AH->>RT: Execute reply/resolve/unresolve action

Loading

Possibly related PRs

• Fix bug with not handling cold email follow up properly #322: Implements similar modifications to cold email handling by introducing and utilizing the messageId in email processing functions.

Poem

I'm a rabbit quick on my feet,
Hopping through code with a rhythmic beat,
Message IDs now lead the way,
Guiding keys that dance and play,
Bugs nibble away in the warm night air,
A code-hop celebration beyond compare! 🐇

---

📜 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 d0e2211 and 7d9b34e.

📒 Files selected for processing (10)

• apps/web/app/(app)/cold-email-blocker/TestRules.tsx (2 hunks)
• apps/web/app/(app)/reply-tracker/ReplyTrackerEmails.tsx (3 hunks)
• apps/web/app/api/ai/categorize/controller.ts (2 hunks)
• apps/web/app/api/ai/categorize/validation.ts (1 hunks)
• apps/web/components/email-list/EmailList.tsx (1 hunks)
• apps/web/hooks/useTableKeyboardNavigation.ts (1 hunks)
• apps/web/utils/actions/cold-email.ts (1 hunks)
• apps/web/utils/actions/validation.ts (1 hunks)
• apps/web/utils/cold-email/is-cold-email.ts (3 hunks)
• apps/web/utils/gmail/message.ts (2 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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. (Beta)
• @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.