Skip to content

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

Merged
merged 1 commit into from
Jun 27, 2025

Conversation

arcoraven
Copy link
Contributor

@arcoraven arcoraven commented Jun 27, 2025

[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 the payload field. This change aligns with the webhook documentation referenced in the code comment.

Key changes:

  • Renamed payload field to data in the WebhookEvent interface
  • Changed the type from Record<string, unknown>[] to Record<string, unknown>
  • Removed the assertion that checked for non-empty payload arrays
  • Added a more descriptive comment linking to the webhook documentation

How to test

Verify that webhook events are properly structured with the new schema when produced.

Summary by CodeRabbit

  • Chores
    • Updated the structure of webhook payloads so that data is now provided as an object instead of an array. This change improves consistency in webhook event data formatting.

PR-Codex overview

This PR focuses on updating the WebhookEvent interface in the service-utils package to change the payload property to data and modify its structure, as well as enhancing the documentation for webhook events.

Detailed summary

  • Changed the property name from payload to data in the WebhookEvent interface.
  • Updated the type of data from Record<string, unknown>[] to Record<string, unknown>.
  • Removed the assertion that payload must not be empty in the sendEvents method.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Copy link

vercel bot commented Jun 27, 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 Jun 27, 2025 6:21pm
nebula ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 27, 2025 6:21pm
thirdweb_playground ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 27, 2025 6:21pm
thirdweb-www ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 27, 2025 6:21pm
wallet-ui ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 27, 2025 6:21pm

Copy link

changeset-bot bot commented Jun 27, 2025

🦋 Changeset detected

Latest commit: ede38a2

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@thirdweb-dev/service-utils Patch

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

Copy link
Contributor

coderabbitai bot commented Jun 27, 2025

Walkthrough

This change updates the webhook event structure in the @thirdweb-dev/service-utils package by replacing the payload array with a single data object in the WebhookEvent interface and adjusts the WebhookEventProducer logic accordingly. A changeset is added to document this patch update.

Changes

File(s) Change Summary
.changeset/mean-jars-cheat.md Added a changeset documenting the patch update for the webhook payload structure change.
packages/service-utils/src/node/webhookProducer.ts Replaced payload array with data object in WebhookEvent interface and updated logic in WebhookEventProducer.

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
Loading

Possibly related PRs


📜 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 6e7b663 and ede38a2.

📒 Files selected for processing (2)
  • .changeset/mean-jars-cheat.md (1 hunks)
  • packages/service-utils/src/node/webhookProducer.ts (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • .changeset/mean-jars-cheat.md
  • packages/service-utils/src/node/webhookProducer.ts
⏰ Context from checks skipped due to timeout of 90000ms (8)
  • GitHub Check: E2E Tests (pnpm, webpack)
  • GitHub Check: Size
  • GitHub Check: Lint Packages
  • GitHub Check: Build Packages
  • GitHub Check: Unit Tests
  • GitHub Check: E2E Tests (pnpm, vite)
  • GitHub Check: E2E Tests (pnpm, esbuild)
  • GitHub Check: Analyze (javascript)
✨ 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need 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)

  • @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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @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 Author


How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • merge-queue - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

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.

@arcoraven arcoraven marked this pull request as ready for review June 27, 2025 18:02
@arcoraven arcoraven requested a review from a team as a code owner June 27, 2025 18:02
Copy link

codecov bot commented Jun 27, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 51.92%. Comparing base (e814248) to head (ede38a2).
Report is 1 commits behind head on main.

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           
Flag Coverage Δ
packages 51.92% <ø> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

github-actions bot commented Jun 27, 2025

size-limit report 📦

Path Size Loading time (3g) Running time (snapdragon) Total time
thirdweb (esm) 63.11 KB (0%) 1.3 s (0%) 278 ms (+135.55% 🔺) 1.6 s
thirdweb (cjs) 352.61 KB (0%) 7.1 s (0%) 1.1 s (+14.78% 🔺) 8.1 s
thirdweb (minimal + tree-shaking) 5.72 KB (0%) 115 ms (0%) 123 ms (+1822.65% 🔺) 237 ms
thirdweb/chains (tree-shaking) 530 B (0%) 11 ms (0%) 64 ms (+1722.42% 🔺) 74 ms
thirdweb/react (minimal + tree-shaking) 19.59 KB (0%) 392 ms (0%) 105 ms (+430.14% 🔺) 497 ms

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant