-
Notifications
You must be signed in to change notification settings - Fork 557
chore: change webhook back to object #7461
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
🦋 Changeset detectedLatest commit: ede38a2 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
WalkthroughThis change updates the webhook event structure in the Changes
Sequence Diagram(s)sequenceDiagram
participant Client
participant WebhookEventProducer
participant KafkaProducer
Client->>WebhookEventProducer: sendEvents({ teamId, data, ... })
WebhookEventProducer->>WebhookEventProducer: Validate teamId, projectId, etc.
WebhookEventProducer->>KafkaProducer: Send event with data as object
Possibly related PRs
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (2)
⏰ Context from checks skipped due to timeout of 90000ms (8)
✨ Finishing Touches
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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 (
|
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7461 +/- ##
=======================================
Coverage 51.92% 51.92%
=======================================
Files 947 947
Lines 63932 63932
Branches 4216 4216
=======================================
Hits 33194 33194
Misses 30632 30632
Partials 106 106
🚀 New features to boost your workflow:
|
size-limit report 📦
|
6e7b663
to
ede38a2
Compare
[Service-Utils] Fix: Update webhook payload structure
Notes for the reviewer
This PR updates the webhook event schema to use a single
data
object instead of an array of objects in thepayload
field. This change aligns with the webhook documentation referenced in the code comment.Key changes:
payload
field todata
in theWebhookEvent
interfaceRecord<string, unknown>[]
toRecord<string, unknown>
How to test
Verify that webhook events are properly structured with the new schema when produced.
Summary by CodeRabbit
PR-Codex overview
This PR focuses on updating the
WebhookEvent
interface in theservice-utils
package to change thepayload
property todata
and modify its structure, as well as enhancing the documentation for webhook events.Detailed summary
payload
todata
in theWebhookEvent
interface.data
fromRecord<string, unknown>[]
toRecord<string, unknown>
.payload
must not be empty in thesendEvents
method.