Skip to content

[SDK] Fix: Webhook Schema #7151

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
May 23, 2025
Merged

[SDK] Fix: Webhook Schema #7151

merged 1 commit into from
May 23, 2025

Conversation

gregfromstl
Copy link
Member

@gregfromstl gregfromstl commented May 23, 2025


PR-Codex overview

This PR focuses on updating the Webhook schema in the thirdweb package to enhance the structure of the originToken and destinationToken properties, transitioning from simple address strings to detailed objects containing various attributes.

Detailed summary

  • Updated originToken and destinationToken from string to object structure in Webhook.ts.
  • Added properties to originToken and destinationToken: chainId, address, name, symbol, decimals, priceUsd, and iconUri.
  • Adjusted corresponding test cases in Webhook.test.ts to reflect the new object structure.

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

Summary by CodeRabbit

  • Bug Fixes
    • Enhanced webhook support to include detailed token information such as chain ID, name, symbol, decimals, price, and icon for origin and destination tokens.
  • Tests
    • Updated test data to match the new detailed token structure in webhook payloads.
  • Chores
    • Added a changeset to document this patch update.

@gregfromstl gregfromstl requested review from a team as code owners May 23, 2025 22:46
Copy link

changeset-bot bot commented May 23, 2025

🦋 Changeset detected

Latest commit: 5277edd

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

This PR includes changesets to release 2 packages
Name Type
thirdweb Patch
@thirdweb-dev/wagmi-adapter 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

vercel bot commented May 23, 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 May 23, 2025 11:18pm
login ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 23, 2025 11:18pm
thirdweb_playground ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 23, 2025 11:18pm
thirdweb-www ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 23, 2025 11:18pm
wallet-ui ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 23, 2025 11:18pm

Copy link

coderabbitai bot commented May 23, 2025

Walkthrough

The changes update the webhook schema for token fields from simple address strings to detailed token objects containing multiple properties. Corresponding test fixtures are modified to match the new schema. Additionally, a changeset file is added to document the patch update for the affected package.

Changes

File(s) Change Summary
.changeset/purple-wasps-sort.md Added a changeset file documenting a patch update for the "thirdweb" package regarding the webhook schema type fix.
packages/thirdweb/src/bridge/Webhook.ts Updated the webhook schema: originToken and destinationToken fields now require detailed token objects instead of address strings.
packages/thirdweb/src/bridge/Webhook.test.ts Modified test fixtures to use detailed token objects for originToken and destinationToken fields.

Sequence Diagram(s)

sequenceDiagram
    participant WebhookSource
    participant WebhookParser
    participant TokenObject

    WebhookSource->>WebhookParser: Send webhook payload (with originToken & destinationToken as objects)
    WebhookParser->>TokenObject: Validate token fields (chainId, address, name, symbol, decimals, priceUsd, iconUri)
    WebhookParser-->>WebhookSource: Return parsed and validated webhook data
Loading

Suggested reviewers

  • gregfromstl

Warning

Review ran into problems

🔥 Problems

Errors were encountered while retrieving linked issues.

Errors (1)
  • TEAM-0000: Entity not found: Issue - Could not find referenced Issue.

📜 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 8bafd3f and 5277edd.

📒 Files selected for processing (3)
  • .changeset/purple-wasps-sort.md (1 hunks)
  • packages/thirdweb/src/bridge/Webhook.test.ts (1 hunks)
  • packages/thirdweb/src/bridge/Webhook.ts (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (3)
  • packages/thirdweb/src/bridge/Webhook.test.ts
  • packages/thirdweb/src/bridge/Webhook.ts
  • .changeset/purple-wasps-sort.md
✨ 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

graphite-app bot commented May 23, 2025

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.

@github-actions github-actions bot added packages SDK Involves changes to the thirdweb SDK labels May 23, 2025
@gregfromstl gregfromstl force-pushed the greg/fix-ub-webhook-schema branch from 3752c01 to defc808 Compare May 23, 2025 22:46
Copy link

@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: 0

🧹 Nitpick comments (2)
packages/thirdweb/src/bridge/Webhook.test.ts (2)

31-49: Test fixtures correctly updated for new schema.

The test data properly reflects the new token object structure with all required fields.

Consider using different values for originToken and destinationToken to better simulate real-world scenarios where users might be swapping between different tokens.

       originToken: {
         chainId: 1,
         address: "0x1234567890123456789012345678901234567890" as const,
-        name: "Token",
-        symbol: "TKN",
+        name: "Ethereum",
+        symbol: "ETH",
         decimals: 18,
         priceUsd: 1.0,
         iconUri: "https://example.com/icon.png",
       },
       originAmount: "1.0",
       destinationToken: {
         chainId: 1,
-        address: "0x1234567890123456789012345678901234567890" as const,
-        name: "Token",
-        symbol: "TKN",
-        decimals: 18,
-        priceUsd: 1.0,
+        address: "0xA0b86a33E6441e0aE0Ac3D9Ba4C7A7f5b0e8Bb5A" as const,
+        name: "USD Coin",
+        symbol: "USDC", 
+        decimals: 6,
+        priceUsd: 1.0,
         iconUri: "https://example.com/icon.png",
       },

288-306: Fix misleading test comment.

The comment mentions "invalid hex address" but the test is actually validating type mismatch (string vs object). The address validation would occur within the token object schema.

-    it("should throw error for invalid hex address", async () => {
+    it("should throw error for invalid destinationToken type", async () => {
       const invalidPayload = {
         version: 2,
         data: {
           ...validPayload.data,
-          destinationToken: "invalid-address", // Invalid hex address
+          destinationToken: "invalid-address", // Should be object, not string
         },
       };
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3489ece and defc808.

📒 Files selected for processing (3)
  • .changeset/purple-wasps-sort.md (1 hunks)
  • packages/thirdweb/src/bridge/Webhook.test.ts (1 hunks)
  • packages/thirdweb/src/bridge/Webhook.ts (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (8)
  • GitHub Check: Unit Tests
  • GitHub Check: Build Packages
  • GitHub Check: E2E Tests (pnpm, esbuild)
  • GitHub Check: Lint Packages
  • GitHub Check: Size
  • GitHub Check: E2E Tests (pnpm, webpack)
  • GitHub Check: E2E Tests (pnpm, vite)
  • GitHub Check: Analyze (javascript)
🔇 Additional comments (2)
packages/thirdweb/src/bridge/Webhook.ts (1)

26-44: Excellent schema enhancement!

The update from simple address strings to comprehensive token objects significantly improves the webhook data richness. The new schema properly includes all essential token metadata (chainId, address, name, symbol, decimals, priceUsd, iconUri) with appropriate type validation.

.changeset/purple-wasps-sort.md (1)

1-6: Changeset properly documents the schema update.

The changeset correctly identifies this as a patch update and provides an appropriate description for the webhook schema enhancement.

Copy link
Contributor

github-actions bot commented May 23, 2025

size-limit report 📦

Path Size Loading time (3g) Running time (snapdragon) Total time
thirdweb (esm) 61.75 KB (+0.1% 🔺) 1.3 s (+0.1% 🔺) 493 ms (+85.08% 🔺) 1.8 s
thirdweb (cjs) 344.4 KB (-0.06% 🔽) 6.9 s (-0.06% 🔽) 2.2 s (+0.58% 🔺) 9 s
thirdweb (minimal + tree-shaking) 5.69 KB (0%) 114 ms (0%) 175 ms (+913.57% 🔺) 289 ms
thirdweb/chains (tree-shaking) 531 B (0%) 11 ms (0%) 71 ms (+1158.51% 🔺) 82 ms
thirdweb/react (minimal + tree-shaking) 19.54 KB (0%) 391 ms (0%) 228 ms (+374.51% 🔺) 618 ms

Copy link

codecov bot commented May 23, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.70%. Comparing base (6c180b5) to head (5277edd).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #7151      +/-   ##
==========================================
+ Coverage   55.68%   55.70%   +0.01%     
==========================================
  Files         904      904              
  Lines       58324    58340      +16     
  Branches     4113     4115       +2     
==========================================
+ Hits        32476    32496      +20     
+ Misses      25743    25739       -4     
  Partials      105      105              
Flag Coverage Δ
packages 55.70% <100.00%> (+0.01%) ⬆️
Files with missing lines Coverage Δ
packages/thirdweb/src/bridge/Webhook.ts 100.00% <100.00%> (ø)

... and 4 files with indirect coverage changes

🚀 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.

@gregfromstl gregfromstl force-pushed the greg/fix-ub-webhook-schema branch from f0b2288 to 8bafd3f Compare May 23, 2025 22:56
Copy link
Contributor

graphite-app bot commented May 23, 2025

Merge activity

<!--

## title your PR with this format: "[SDK/Dashboard/Portal] Feature/Fix: Concise title for the changes"

If you did not copy the branch name from Linear, paste the issue tag here (format is TEAM-0000):

## Notes for the reviewer

Anything important to call out? Be sure to also clarify these in your comments.

## How to test

Unit tests, playground, etc.

-->

<!-- start pr-codex -->

---

## PR-Codex overview
This PR focuses on updating the `Webhook` schema in the `thirdweb` package to enhance the structure of `originToken` and `destinationToken` by replacing simple address strings with detailed objects containing additional properties.

### Detailed summary
- Updated `originToken` and `destinationToken` to be objects with properties:
  - `chainId`
  - `address`
  - `name`
  - `symbol`
  - `decimals`
  - `priceUsd`
  - `iconUri`
- Adjusted the test file to reflect these changes with appropriate object structures.

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

<!-- end pr-codex -->

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit

- **Bug Fixes**
  - Enhanced webhook support to include detailed token information such as chain ID, name, symbol, decimals, price, and icon for origin and destination tokens.
- **Tests**
  - Updated test data to match the new detailed token structure in webhook payloads.
- **Chores**
  - Added a changeset to document this patch update.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
packages SDK Involves changes to the thirdweb SDK
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants