Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added shortcuts in /mail #392

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Saksham1387
Copy link

@Saksham1387 Saksham1387 commented Apr 6, 2025

Fixes: #343

I have added the mentioned shortcuts

E --> archive
R --> Reply

and have also added Arrow up/down

Screenshot 2025-04-06 at 23 54 20

Summary by CodeRabbit

  • New Features
    • Introduced keyboard navigation for the email list, allowing users to reply and archive emails quickly using the keyboard.
    • Enhanced visual cues now clearly indicate the currently selected email thread for an improved user experience.

Copy link

vercel bot commented Apr 6, 2025

@Saksham1387 is attempting to deploy a commit to the Inbox Zero Team on Vercel.

A member of the Team first needs to authorize it.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Copy link
Contributor

coderabbitai bot commented Apr 6, 2025

Walkthrough

The changes add keyboard navigation to the EmailList component. A new custom hook, useEmailListKeyboardNav, manages keyboard actions for replying and archiving email threads. The mapping over threads now includes an index to visualize the focused state, and the handleAction function is updated accordingly. The previous keyboard event listener hook has been removed in favor of the new encapsulated approach.

Changes

File(s) Summary of Changes
apps/web/components/…/EmailList.tsx - Added useEmailListKeyboardNav hook to manage keyboard interactions.
- Updated threads.map to include the index parameter for focus handling.
- Revised handleAction function for "reply" and "archive" actions.
- Removed the old useEffect for keyboard event listeners.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant EmailList
    participant KeyboardNav

    User->>EmailList: Press key (R, E, or Arrow)
    EmailList->>KeyboardNav: Handle key event via hook
    KeyboardNav->>EmailList: Trigger action (reply/archive or update focus)
    EmailList->>User: Update UI with focused thread/action executed
Loading

Assessment against linked issues

Objective Addressed Explanation
Mail: Add keyboard shortcuts (#343)

Possibly related PRs

Suggested reviewers

  • elie222

Poem

In the world of code, I happily hop,
Adding shortcuts that make the UI pop.
With keys to reply and archive on cue,
Each press a little dance, so fresh and new.
Cheers from a rabbit, in this code breakthrough! 🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

Scope: all 2 workspace projects
 WARN  GET http://10.0.0.28:4873/turbo error (503). Will retry in 10 seconds. 2 retries left.
 WARN  GET http://10.0.0.28:4873/eslint/-/eslint-9.23.0.tgz error (ERR_PNPM_FETCH_503). Will retry in 10 seconds. 2 retries left.
 WARN  GET http://10.0.0.28:4873/@vercel/style-guide/-/style-guide-6.0.0.tgz error (ERR_PNPM_FETCH_503). Will retry in 10 seconds. 2 retries left.
 WARN  GET http://10.0.0.28:4873/eslint-plugin-only-warn/-/eslint-plugin-only-warn-1.1.0.tgz error (ERR_PNPM_FETCH_503). Will retry in 10 seconds. 2 retries left.
 WARN  GET http://10.0.0.28:4873/typescript/-/typescript-5.8.2.tgz error (ERR_PNPM_FETCH_503). Will retry in 10 seconds. 2 retries left.
 WARN  GET http://10.0.0.28:4873/@typescript-eslint/parser/-/parser-8.28.0.tgz error (ERR_PNPM_FETCH_503). Will retry in 10 seconds. 2 retries left.
 WARN  GET http://10.0.0.28:4873/eslint-config-prettier/-/eslint-config-prettier-10.1.1.tgz error (ERR_PNPM_FETCH_503). Will retry in 10 seconds. 2 retries left.
 WARN  GET http://10.0.0.28:4873/eslint-config-turbo/-/eslint-config-turbo-2.4.4.tgz error (ERR_PNPM_FETCH_503). Will retry in 10 seconds. 2 retries left.
 WARN  GET http://10.0.0.28:4873/turbo/-/turbo-2.4.4.tgz error (ERR_PNPM_FETCH_503). Will retry in 10 seconds. 2 retries left.
 WARN  GET http://10.0.0.28:4873/@typescript-eslint/eslint-plugin/-/eslint-plugin-8.28.0.tgz error (ERR_PNPM_FETCH_503). Will retry in 10 seconds. 2 retries left.
 WARN  GET http://10.0.0.28:4873/prettier/-/prettier-3.5.3.tgz error (ERR_PNPM_FETCH_503). Will retry in 10 seconds. 2 retries left.
 WARN  GET http://10.0.0.28:4873/turbo error (503). Will retry in 1 minute. 1 retries left.
 WARN  GET http://10.0.0.28:4873/eslint/-/eslint-9.23.0.tgz error (ERR_PNPM_FETCH_503). Will retry in 1 minute. 1 retries left.
 WARN  GET http://10.0.0.28:4873/@vercel/style-guide/-/style-guide-6.0.0.tgz error (ERR_PNPM_FETCH_503). Will retry in 1 minute. 1 retries left.
 WARN  GET http://10.0.0.28:4873/eslint-plugin-only-warn/-/eslint-plugin-only-warn-1.1.0.tgz error (ERR_PNPM_FETCH_503). Will retry in 1 minute. 1 retries left.
 WARN  GET http://10.0.0.28:4873/typescript/-/typescript-5.8.2.tgz error (ERR_PNPM_FETCH_503). Will retry in 1 minute. 1 retries left.
 WARN  GET http://10.0.0.28:4873/@typescript-eslint/parser/-/parser-8.28.0.tgz error (ERR_PNPM_FETCH_503). Will retry in 1 minute. 1 retries left.
 WARN  GET http://10.0.0.28:4873/eslint-config-prettier/-/eslint-config-prettier-10.1.1.tgz error (ERR_PNPM_FETCH_503). Will retry in 1 minute. 1 retries left.
 WARN  GET http://10.0.0.28:4873/eslint-config-turbo/-/eslint-config-turbo-2.4.4.tgz error (ERR_PNPM_FETCH_503). Will retry in 1 minute. 1 retries left.
 WARN  GET http://10.0.0.28:4873/turbo/-/turbo-2.4.4.tgz error (ERR_PNPM_FETCH_503). Will retry in 1 minute. 1 retries left.
 WARN  GET http://10.0.0.28:4873/@typescript-eslint/eslint-plugin/-/eslint-plugin-8.28.0.tgz error (ERR_PNPM_FETCH_503). Will retry in 1 minute. 1 retries left.
 WARN  GET http://10.0.0.28:4873/prettier/-/prettier-3.5.3.tgz error (ERR_PNPM_FETCH_503). Will retry in 1 minute. 1 retries left.
/tmp/eslint/packages/eslint-config:
 ERR_PNPM_FETCH_503  GET http://10.0.0.28:4873/eslint-plugin-only-warn/-/eslint-plugin-only-warn-1.1.0.tgz: Service Unavailable - 503

This error happened while installing a direct dependency of /tmp/eslint/packages/eslint-config

✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 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.

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: 1

🧹 Nitpick comments (2)
apps/web/components/email-list/EmailList.tsx (2)

387-397: Consider adding visual confirmation for keyboard shortcuts

While the keyboard shortcuts work well, users might benefit from a visual confirmation (e.g., a toast notification) when using the 'R' shortcut for reply.

Consider adding a toast notification:

if (e.key === "r" || e.key === "R") {
  if (isCmdOrCtrl) {
    e.preventDefault();
  }
  const thread = threads[focusedIndex];
  if (thread) {
    setOpenThreadId(thread.id);
    markReadThreads([thread.id], () => refetch());
    scrollToId(thread.id);
+   toast.info("Replying to email");
  }
}

373-375: Consider adding support for contentEditable elements

The keyboard event handler checks for INPUT and TEXTAREA elements, but it doesn't check for contentEditable elements, which might be used in rich text components.

if (
  document.activeElement?.tagName === "INPUT" ||
  document.activeElement?.tagName === "TEXTAREA" ||
+ document.activeElement?.getAttribute("contenteditable") === "true"
)
  return;
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1c8d51b and 8a99439.

📒 Files selected for processing (2)
  • apps/web/components/email-list/EmailList.tsx (4 hunks)
  • apps/web/components/email-list/EmailListItem.tsx (2 hunks)
🧰 Additional context used
🪛 Biome (1.9.4)
apps/web/components/email-list/EmailList.tsx

[error] 369-369: This hook does not specify all of its dependencies: scrollToId

This dependency is not specified in the hook dependency list.

(lint/correctness/useExhaustiveDependencies)

🔇 Additional comments (7)
apps/web/components/email-list/EmailListItem.tsx (3)

29-29: LGTM: Added focused prop to EmailListItem

The optional focused prop correctly extends the component's interface to support keyboard navigation state.


79-81: Hover styling correctly handles focused state

The conditional styling for hover effects now properly considers the focused state, ensuring appropriate visual feedback during keyboard navigation.


85-85: Good visual indication for keyboard focus

The z-index and ring styling provide clear visual feedback for the currently focused item during keyboard navigation, improving accessibility.

apps/web/components/email-list/EmailList.tsx (4)

367-368: LGTM: Added focusedIndex state for keyboard navigation

The state variable is correctly initialized to track the currently focused email in the list.


370-408: Well-implemented keyboard shortcuts

The implementation of keyboard shortcuts is clean and follows good practices:

  • Proper checks to avoid interfering with input fields
  • Clear usage of arrow keys for navigation
  • Command/Control + 'R' for reply (opens the thread)
  • Command/Control + 'E' for archive

This directly addresses the PR objectives to enhance keyboard navigation.


493-493: Correctly passing index to map function

Adding the index parameter to the map function enables tracking the currently focused item.


505-505: Properly passing focused state to EmailListItem

The focused state is correctly passed to the EmailListItem component based on the focusedIndex.

Comment on lines 369 to 412
useEffect(() => {
function handleKeyDown(e: KeyboardEvent) {
if (
document.activeElement?.tagName === "INPUT" ||
document.activeElement?.tagName === "TEXTAREA"
)
return;

const isCmdOrCtrl = e.metaKey || e.ctrlKey;

if (e.key === "ArrowDown") {
setFocusedIndex((prev) => Math.min(prev + 1, threads.length - 1));
}

if (e.key === "ArrowUp") {
setFocusedIndex((prev) => Math.max(prev - 1, 0));
}

if (e.key === "r" || e.key === "R") {
if (isCmdOrCtrl) {
e.preventDefault();
}
const thread = threads[focusedIndex];
if (thread) {
setOpenThreadId(thread.id);
markReadThreads([thread.id], () => refetch());
scrollToId(thread.id);
}
}

if (e.key === "e" || e.key === "E") {
if (isCmdOrCtrl) {
e.preventDefault();
}
const thread = threads[focusedIndex];
if (thread) {
onArchive(thread);
}
}
}

window.addEventListener("keydown", handleKeyDown);
return () => window.removeEventListener("keydown", handleKeyDown);
}, [threads, focusedIndex, setOpenThreadId, onArchive, refetch]);
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Missing dependency in useEffect dependency array

The scrollToId function is used inside the effect but is not included in the dependency array, which could lead to stale closures.

Update the dependency array to include all dependencies:

- }, [threads, focusedIndex, setOpenThreadId, onArchive, refetch]);
+ }, [threads, focusedIndex, setOpenThreadId, onArchive, refetch, scrollToId]);
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
useEffect(() => {
function handleKeyDown(e: KeyboardEvent) {
if (
document.activeElement?.tagName === "INPUT" ||
document.activeElement?.tagName === "TEXTAREA"
)
return;
const isCmdOrCtrl = e.metaKey || e.ctrlKey;
if (e.key === "ArrowDown") {
setFocusedIndex((prev) => Math.min(prev + 1, threads.length - 1));
}
if (e.key === "ArrowUp") {
setFocusedIndex((prev) => Math.max(prev - 1, 0));
}
if (e.key === "r" || e.key === "R") {
if (isCmdOrCtrl) {
e.preventDefault();
}
const thread = threads[focusedIndex];
if (thread) {
setOpenThreadId(thread.id);
markReadThreads([thread.id], () => refetch());
scrollToId(thread.id);
}
}
if (e.key === "e" || e.key === "E") {
if (isCmdOrCtrl) {
e.preventDefault();
}
const thread = threads[focusedIndex];
if (thread) {
onArchive(thread);
}
}
}
window.addEventListener("keydown", handleKeyDown);
return () => window.removeEventListener("keydown", handleKeyDown);
}, [threads, focusedIndex, setOpenThreadId, onArchive, refetch]);
useEffect(() => {
function handleKeyDown(e: KeyboardEvent) {
if (
document.activeElement?.tagName === "INPUT" ||
document.activeElement?.tagName === "TEXTAREA"
)
return;
const isCmdOrCtrl = e.metaKey || e.ctrlKey;
if (e.key === "ArrowDown") {
setFocusedIndex((prev) => Math.min(prev + 1, threads.length - 1));
}
if (e.key === "ArrowUp") {
setFocusedIndex((prev) => Math.max(prev - 1, 0));
}
if (e.key === "r" || e.key === "R") {
if (isCmdOrCtrl) {
e.preventDefault();
}
const thread = threads[focusedIndex];
if (thread) {
setOpenThreadId(thread.id);
markReadThreads([thread.id], () => refetch());
scrollToId(thread.id);
}
}
if (e.key === "e" || e.key === "E") {
if (isCmdOrCtrl) {
e.preventDefault();
}
const thread = threads[focusedIndex];
if (thread) {
onArchive(thread);
}
}
}
window.addEventListener("keydown", handleKeyDown);
return () => window.removeEventListener("keydown", handleKeyDown);
}, [threads, focusedIndex, setOpenThreadId, onArchive, refetch, scrollToId]);
🧰 Tools
🪛 Biome (1.9.4)

[error] 369-369: This hook does not specify all of its dependencies: scrollToId

This dependency is not specified in the hook dependency list.

(lint/correctness/useExhaustiveDependencies)

@elie222
Copy link
Owner

elie222 commented Apr 6, 2025

would take a look at how we do this in other places in the codebase to keep consistency.
eg:

  • apps/web/hooks/useTableKeyboardNavigation.ts
  • apps/web/app/(app)/reply-zero/ReplyTrackerEmails.tsx

@Saksham1387
Copy link
Author

I made the required changes and changed the implementation same as it is been done in other places

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: 1

🧹 Nitpick comments (3)
apps/web/components/email-list/EmailList.tsx (3)

368-411: Consider removing commented-out code

The PR has left a significant block of commented-out code. While this can be helpful during development and testing, it's generally a good practice to remove commented-out code before merging to production to keep the codebase clean.


413-413: Remove unused state declaration

This commented-out line can be removed along with the other commented code to maintain cleanliness.


595-613: Consider adding prop to disable keyboard navigation in certain contexts

For better user experience, consider adding a prop to disable keyboard navigation when the user is:

  • Focusing on input fields outside of the email list
  • Using keyboard shortcuts that might conflict with the email navigation

This would prevent unexpected actions when users are interacting with other parts of the interface.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8a99439 and bf690d1.

📒 Files selected for processing (1)
  • apps/web/components/email-list/EmailList.tsx (6 hunks)
🧰 Additional context used
🪛 Biome (1.9.4)
apps/web/components/email-list/EmailList.tsx

[error] 415-415: This hook does not specify all of its dependencies: onArchive

This dependency is not specified in the hook dependency list.

(lint/correctness/useExhaustiveDependencies)


[error] 415-415: This hook does not specify all of its dependencies: refetch

This dependency is not specified in the hook dependency list.

(lint/correctness/useExhaustiveDependencies)


[error] 415-415: This hook does not specify all of its dependencies: scrollToId

This dependency is not specified in the hook dependency list.

(lint/correctness/useExhaustiveDependencies)

🔇 Additional comments (4)
apps/web/components/email-list/EmailList.tsx (4)

595-613: Good implementation of the keyboard navigation hook

The implementation of useEmailListKeyboardNav is clean and follows best practices by:

  1. Delegating to the reusable useTableKeyboardNavigation hook
  2. Using a callback function (handleKeyAction) with proper dependency array
  3. Maintaining a clear separation of concerns

This approach makes the code more maintainable and reusable.


431-431: Effective integration of keyboard navigation

Good job integrating the custom hook with the existing component. This cleanly replaces the previous commented-out implementation with a more modular approach.


512-513: Correctly passing index to map function and using it for selection state

The addition of the index parameter to the map function and using it to determine the selected state in EmailListItem is the right approach for implementing keyboard navigation.

Also applies to: 537-537


3-3: Ensure imports are properly used

The import line has been updated to add new hooks. Make sure all imported hooks are being used in the component; otherwise, they should be removed.

Comment on lines +415 to +429
const handleAction = useCallback(
async (index: number, action: "reply" | "archive") => {
const thread = threads[index];
if (!thread) return;

if (action === "reply") {
setOpenThreadId(thread.id);
markReadThreads([thread.id], () => refetch());
scrollToId(thread.id);
} else if (action === "archive") {
onArchive(thread);
}
},
[threads, setOpenThreadId],
);
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Missing dependencies in useCallback dependency array

The handleAction callback has missing dependencies in its dependency array:

- }, [threads, setOpenThreadId],
+ }, [threads, setOpenThreadId, onArchive, refetch, scrollToId],

These dependencies are used inside the callback but not included in the dependency array, which could lead to stale closures and unexpected behavior.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
const handleAction = useCallback(
async (index: number, action: "reply" | "archive") => {
const thread = threads[index];
if (!thread) return;
if (action === "reply") {
setOpenThreadId(thread.id);
markReadThreads([thread.id], () => refetch());
scrollToId(thread.id);
} else if (action === "archive") {
onArchive(thread);
}
},
[threads, setOpenThreadId],
);
const handleAction = useCallback(
async (index: number, action: "reply" | "archive") => {
const thread = threads[index];
if (!thread) return;
if (action === "reply") {
setOpenThreadId(thread.id);
markReadThreads([thread.id], () => refetch());
scrollToId(thread.id);
} else if (action === "archive") {
onArchive(thread);
}
},
[threads, setOpenThreadId, onArchive, refetch, scrollToId],
);
🧰 Tools
🪛 Biome (1.9.4)

[error] 415-415: This hook does not specify all of its dependencies: onArchive

This dependency is not specified in the hook dependency list.

(lint/correctness/useExhaustiveDependencies)


[error] 415-415: This hook does not specify all of its dependencies: refetch

This dependency is not specified in the hook dependency list.

(lint/correctness/useExhaustiveDependencies)


[error] 415-415: This hook does not specify all of its dependencies: scrollToId

This dependency is not specified in the hook dependency list.

(lint/correctness/useExhaustiveDependencies)

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.

Mail: Add keyboard shortcuts
3 participants