-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Update SDK with new endpoints for triggers #15385
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
Conversation
* Add new methods to manipulate deployed Connect triggers * Document the new methods (JSDoc only) * Bump minor version
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Skipped Deployments
|
|
@jverce is attempting to deploy a commit to the Pipedreamers Team on Vercel. A member of the Team first needs to authorize it. |
|
Warning Rate limit exceeded@jverce has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 22 minutes and 23 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
WalkthroughThis pull request introduces significant enhancements to the Pipedream SDK, focusing on expanding trigger management capabilities. The changes include adding new type definitions and methods in the SDK's shared components, specifically introducing comprehensive trigger-related operations. The package version has been bumped from 1.1.6 to 1.2.0, reflecting the substantial functional improvements. Changes
Sequence DiagramsequenceDiagram
participant Client
participant SDK
participant TriggerService
Client->>SDK: getTriggers()
SDK->>TriggerService: Request trigger list
TriggerService-->>SDK: Return trigger details
SDK-->>Client: Provide trigger information
Client->>SDK: updateTriggerWorkflows()
SDK->>TriggerService: Update trigger workflows
TriggerService-->>SDK: Confirm update
SDK-->>Client: Return update result
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this 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 (4)
packages/sdk/src/shared/index.ts (2)
651-652: Correct the grammatical error in JSDoc forworkflowIds.The comment should read: "The workflow IDs that should receive events emitted by the trigger."
679-680: Correct the grammatical error in JSDoc forwebhookUrls.The comment should read: "The webhook URLs that should receive events emitted by the trigger."
packages/sdk/src/shared/component.ts (2)
116-116: Consider specifying a more precise type for the event payloade.Defining
easRecord<string, any>reduces type safety. If the structure of the event payload is known, consider defining a specific interface or type foreto enhance type checking and maintainability.
121-121: Use a literal type forkif its value is constant.If
kis always"emit", you can define it as a literal typek: "emit";to improve type safety and clarity.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (3)
packages/sdk/package.json(1 hunks)packages/sdk/src/shared/component.ts(1 hunks)packages/sdk/src/shared/index.ts(4 hunks)
✅ Files skipped from review due to trivial changes (1)
- packages/sdk/package.json
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: pnpm publish
Co-authored-by: Danny Roosevelt <[email protected]>
Changelog
WHY
So that the new endpoints in our API are available via the SDK.
Summary by CodeRabbit
Release Notes for @pipedream/sdk v1.2.0
New Features
Improvements
Version Update