moving timer to static props

[dannyroosevelt]

WHY

Summary by CodeRabbit

• Chores
  • Updated versions for the Gmail integration and email notification component.
• New Features
  • Enhanced the email notifications component to consistently include a dedicated polling timer with a default interval.

[vercel]

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

3 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
docs-v2	⬜️ Ignored (Inspect)	Visit Preview		Mar 31, 2025 10:36pm
pipedream-docs	⬜️ Ignored (Inspect)			Mar 31, 2025 10:36pm
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)			Mar 31, 2025 10:36pm

[coderabbitai]

Walkthrough

This pull request updates the version numbers for two Gmail components and revises the export structure. In the root Gmail package, the version is incremented from "0.2.3" to "0.2.4". In the New Email Received component, the version is bumped from "0.2.1" to "0.2.2" and a new timer property is added to the props object, which is now always included regardless of trigger type.

Changes

File(s)	Change Summary
components/gmail/package.json	Version updated from "0.2.3" to "0.2.4".
components/gmail/.../new-email-received.mjs	Version updated from "0.2.1" to "0.2.2"; added a new timer property with type information and default polling intervals; logic modified to always include timer in props.

Sequence Diagram(s)

sequenceDiagram
    participant C as Client
    participant NE as NewEmailReceived Component
    C->>NE: Invoke additionalProps
    NE->>NE: Include timer property unconditionally
    NE-->>C: Return updated props with timer

Loading

Possibly related PRs

• Gmail source improvements #15820: Involves a similar version update in a Gmail package file, suggesting related context in version management.

Suggested labels

User submitted

Suggested reviewers

• michelle0927

Poem

I'm just a bunny hopping in code delight,
Upgrading versions with a twitch so light.
A timer now always hops along in line,
Brighter bytes and carrots intertwine.
Code and carrots—oh, what a sight!
Happy hops to changes done right!

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/sources/new-email-received/new-email-received.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)

---

📜 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 3b13c24 and ca789fa.

📒 Files selected for processing (2)

• components/gmail/package.json (1 hunks)
• components/gmail/sources/new-email-received/new-email-received.mjs (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: pnpm publish
• GitHub Check: Verify TypeScript components
• GitHub Check: Publish TypeScript components

🔇 Additional comments (4)

components/gmail/sources/new-email-received/new-email-received.mjs (3)

18-18: Version increment looks good

Version has been properly incremented from 0.2.1 to 0.2.2 to reflect the changes in this component.

---

36-43: Good refactoring - timer property moved to static props

The timer property has been moved from being conditionally added in the additionalProps() method to being a static property in the main props object. This makes the timer configuration more consistent and always available regardless of trigger type.

---

148-148: Appropriate static property for webhook timer

The static property is now used for the webhook timer configuration, which is a cleaner approach than the previous implementation. This will ensure that the webhook renewal timer is properly configured with a fixed 1-hour interval.

components/gmail/package.json (1)

3-3: Version increment matches component changes

The package version has been properly incremented from 0.2.3 to 0.2.4, which aligns with the changes made to the Gmail component.

✨ 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

• 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.
• @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.