Skip to content

Conversation

@GTFalcao
Copy link
Collaborator

@GTFalcao GTFalcao commented Apr 13, 2025

Closes #16235

Since this is a new action that doesn't affect any existing components, I'm not bumping any component versions, only the package.json version

Summary by CodeRabbit

  • New Features

    • Introduced a new email archiving functionality for Gmail that streamlines moving emails out of the inbox.
  • Chores

    • Updated the application to the latest release version.
    • Added a constant to manage the inbox label efficiently.

@vercel
Copy link

vercel bot commented Apr 13, 2025

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

Name Status Preview Comments Updated (UTC)
docs-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 16, 2025 3:32am
2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
pipedream-docs ⬜️ Ignored (Inspect) Apr 16, 2025 3:32am
pipedream-docs-redirect-do-not-edit ⬜️ Ignored (Inspect) Apr 16, 2025 3:32am

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Apr 13, 2025

Walkthrough

This pull request introduces a new module, gmail-archive-email, that provides an explicit action to archive an email by removing its inbox label. The change utilizes the Gmail API’s updateLabels method, and a new constant INBOX_LABEL_ID (with the value "INBOX") is added to support this functionality. Additionally, the package version has been updated to reflect the new release.

Changes

Files Change Summary
components/gmail/actions/archive-email/.../archive-email.mjs Added new module gmail-archive-email with an asynchronous run method to remove the inbox label from emails.
components/gmail/common/constants.mjs Added the constant INBOX_LABEL_ID with the value "INBOX".
components/gmail/package.json Updated package version from "0.2.10" to "0.3.0".

Sequence Diagram(s)

sequenceDiagram
    participant A as Archive Email Action
    participant G as Gmail API
    A->>G: run() calls updateLabels(message, [INBOX_LABEL_ID])
    G-->>A: Returns response
    A->>A: Generates archive summary message
Loading

Assessment against linked issues

Objective Addressed Explanation
Provide explicit Gmail Archive Email action (#16235)

Poem

I'm a coding rabbit with nimble feet,
Hopping through modules with a rhythmic beat.
Inbox labels vanish with a swish and a flip,
Archiving emails on a joyful script.
Carrots and code, a delicious mix!

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.

components/gmail/actions/archive-email/archive-email.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at packageResolve (node:internal/modules/esm/resolve:839:9)
at moduleResolve (node:internal/modules/esm/resolve:908:18)
at defaultResolve (node:internal/modules/esm/resolve:1038:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:557:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:525:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:246:38)
at ModuleJob._link (node:internal/modules/esm/module_job:126:49)

components/gmail/common/constants.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at packageResolve (node:internal/modules/esm/resolve:839:9)
at moduleResolve (node:internal/modules/esm/resolve:908:18)
at defaultResolve (node:internal/modules/esm/resolve:1038:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:557:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:525:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:246:38)
at ModuleJob._link (node:internal/modules/esm/module_job:126:49)

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)
  • We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.
✨ 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.
    • 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)
components/gmail/common/constants.mjs (1)

8-8: Constant addition is correct and well-implemented.

Adding the INBOX_LABEL_ID constant is appropriate for this feature. The value "INBOX" is the correct system label ID according to Gmail API specifications.

If there are plans to use more Gmail system labels in the future (like SENT, TRASH, etc.), consider creating a structured SYSTEM_LABEL_IDS object instead of individual constants.

-const INBOX_LABEL_ID = "INBOX";
+const SYSTEM_LABEL_IDS = {
+  INBOX: "INBOX",
+  // Other system labels can be added here in the future
+};

 export default {
   USER_ID,
   BODY_TYPES,
   HISTORICAL_EVENTS,
   DEFAULT_LIMIT,
-  INBOX_LABEL_ID,
+  SYSTEM_LABEL_IDS,
 };

Also applies to: 15-15

components/gmail/actions/archive-email/archive-email.mjs (1)

6-7: Consider enhancing the description to clarify archiving behavior.

The current description is accurate but could be more informative about what "archiving" means in Gmail.

-  name: "Archive Email",
-  description: "Archive an email message. [See the documentation](https://developers.google.com/gmail/api/reference/rest/v1/users.messages/modify)",
+  name: "Archive Email",
+  description: "Archive an email message by removing the INBOX label while preserving all other labels. [See the documentation](https://developers.google.com/gmail/api/reference/rest/v1/users.messages/modify)",
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f78b76a and 3956ec4.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (3)
  • components/gmail/actions/archive-email/archive-email.mjs (1 hunks)
  • components/gmail/common/constants.mjs (1 hunks)
  • components/gmail/package.json (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Verify TypeScript components
  • GitHub Check: Publish TypeScript components
  • GitHub Check: pnpm publish
🔇 Additional comments (2)
components/gmail/package.json (1)

3-3: Version bump is appropriate for the feature addition.

The increment from 0.2.10 to 0.3.0 follows semantic versioning conventions, with a minor version increase indicating the addition of a new backward-compatible feature.

components/gmail/actions/archive-email/archive-email.mjs (1)

4-18: Component metadata and props look good.

The component is well-defined with appropriate key, name, description, version, and props. The naming convention follows the pattern of other Gmail actions.

Comment on lines +19 to +34
async run({ $ }) {
const {
gmail,
message,
} = this;

const response = await gmail.updateLabels({
message,
removeLabelIds: [
constants.INBOX_LABEL_ID,
],
});

$.export("$summary", `Successfully archived email (ID: ${message})`);
return response;
},
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Implementation is correct but consider adding error handling.

The implementation correctly uses the Gmail API to remove the INBOX label, effectively archiving the email.

Consider adding error handling to provide better feedback to users:

 async run({ $ }) {
   const {
     gmail,
     message,
   } = this;

-  const response = await gmail.updateLabels({
-    message,
-    removeLabelIds: [
-      constants.INBOX_LABEL_ID,
-    ],
-  });
-
-  $.export("$summary", `Successfully archived email (ID: ${message})`);
-  return response;
+  try {
+    const response = await gmail.updateLabels({
+      message,
+      removeLabelIds: [
+        constants.INBOX_LABEL_ID,
+      ],
+    });
+
+    $.export("$summary", `Successfully archived email (ID: ${message})`);
+    return response;
+  } catch (error) {
+    $.export("$summary", `Failed to archive email: ${error.message}`);
+    throw error;
+  }
 },
📝 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
async run({ $ }) {
const {
gmail,
message,
} = this;
const response = await gmail.updateLabels({
message,
removeLabelIds: [
constants.INBOX_LABEL_ID,
],
});
$.export("$summary", `Successfully archived email (ID: ${message})`);
return response;
},
async run({ $ }) {
const {
gmail,
message,
} = this;
try {
const response = await gmail.updateLabels({
message,
removeLabelIds: [
constants.INBOX_LABEL_ID,
],
});
$.export("$summary", `Successfully archived email (ID: ${message})`);
return response;
} catch (error) {
$.export("$summary", `Failed to archive email: ${error.message}`);
throw error;
}
},

Copy link
Collaborator

@luancazarine luancazarine left a comment

Choose a reason for hiding this comment

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

Hi @GTFalcao, LGTM! Ready for QA!

@dannyroosevelt dannyroosevelt merged commit e84d0d4 into master Apr 16, 2025
9 of 11 checks passed
@dannyroosevelt dannyroosevelt deleted the 16235-gmail-new-action branch April 16, 2025 03:30
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.

[ACTION] Gmail Archive Email action

4 participants