Skip to content

Feature: Add image support to payment links #7129

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 22, 2025

Conversation

gregfromstl
Copy link
Member

@gregfromstl gregfromstl commented May 22, 2025

🤖 Generated with Claude Code


PR-Codex overview

This PR focuses on updating the PaymentLink structure in the application to enhance the attributes it holds, specifically renaming and adding properties to improve clarity and functionality.

Detailed summary

  • In apps/dashboard/src/app/pay/[id]/page.tsx:

    • Renamed paymentLink.label to paymentLink.title.
    • Added paymentLink.imageUrl to the component.
  • In apps/dashboard/src/@/api/universal-bridge/links.ts:

    • Renamed type property label to title.
    • Added property imageUrl to the PaymentLink type.
    • Updated the response mapping to include the new title and imageUrl properties.

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

Summary by CodeRabbit

  • New Features

    • Added support for displaying an image with payment links.
  • Refactor

    • Renamed the payment link label to title for improved clarity in the user interface.

🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <[email protected]>
@gregfromstl gregfromstl requested review from a team as code owners May 22, 2025 19:06
Copy link

linear bot commented May 22, 2025

Copy link

changeset-bot bot commented May 22, 2025

⚠️ No Changeset found

Latest commit: f80a6b8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented May 22, 2025

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

Name Status Preview Comments Updated (UTC)
thirdweb-www ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 22, 2025 7:13pm
4 Skipped Deployments
Name Status Preview Comments Updated (UTC)
docs-v2 ⬜️ Skipped (Inspect) May 22, 2025 7:13pm
login ⬜️ Skipped (Inspect) May 22, 2025 7:13pm
thirdweb_playground ⬜️ Skipped (Inspect) May 22, 2025 7:13pm
wallet-ui ⬜️ Skipped (Inspect) May 22, 2025 7:13pm

Copy link
Contributor

coderabbitai bot commented May 22, 2025

Walkthrough

The changes update the PaymentLink type by renaming the label property to title and adding an optional imageUrl property. Associated logic in the API and UI is adjusted to use the new property names and include the image URL when rendering payment links.

Changes

File(s) Change Summary
apps/dashboard/src/@/api/universal-bridge/links.ts Updated PaymentLink type: renamed label to title, added imageUrl; updated mapping in getPaymentLink to match.
apps/dashboard/src/app/pay/[id]/page.tsx Changed PayPageEmbed prop from paymentLink.label to paymentLink.title and added image prop using paymentLink.imageUrl.

Sequence Diagram(s)

sequenceDiagram
    participant UI as PayPageEmbed Component
    participant API as getPaymentLink Function
    participant Data as PaymentLink Data Source

    UI->>API: Request PaymentLink by ID
    API->>Data: Fetch payment link data
    Data-->>API: Return { title, imageUrl, ... }
    API-->>UI: Return PaymentLink object with title and imageUrl
    UI->>UI: Render PayPageEmbed with title and image
Loading

Possibly related PRs

Suggested labels

Dashboard

Suggested reviewers

  • jnsdls

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 30th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.

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.
✨ 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 22, 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 the Dashboard Involves changes to the Dashboard. label May 22, 2025
Copy link

codecov bot commented May 22, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.61%. Comparing base (526b6b5) to head (f80a6b8).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7129   +/-   ##
=======================================
  Coverage   55.61%   55.61%           
=======================================
  Files         902      902           
  Lines       58177    58177           
  Branches     4085     4085           
=======================================
  Hits        32356    32356           
  Misses      25716    25716           
  Partials      105      105           
Flag Coverage Δ
packages 55.61% <ø> (ø)
🚀 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

@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)
apps/dashboard/src/@/api/universal-bridge/links.ts (1)

40-41: Mapping update is consistent with type changes.

The property mapping in the return object correctly reflects the type changes, using data.title and adding data.imageUrl. This ensures the returned object structure matches the updated PaymentLink type.

However, consider adding validation for the imageUrl to ensure it's a valid URL format before returning it:

return {
  clientId: data.clientId,
  title: data.title,
- imageUrl: data.imageUrl,
+ imageUrl: data.imageUrl && typeof data.imageUrl === 'string' ? data.imageUrl : undefined,
  receiver: data.receiver,
  destinationToken: data.destinationToken,
  amount: data.amount ? BigInt(data.amount) : undefined,
  purchaseData: data.purchaseData,
} as PaymentLink;
apps/dashboard/src/app/pay/[id]/page.tsx (1)

65-66: Component props updated to support image display.

The changes properly align with the updates to the PaymentLink type:

  1. Using paymentLink.title instead of the previous label property
  2. Adding the new image prop with paymentLink.imageUrl

This ensures the PayPageEmbed component receives the necessary data to display both the title and image of the payment link.

You might want to add optional chaining or a fallback for the image prop to handle cases where imageUrl is undefined:

- image={paymentLink.imageUrl}
+ image={paymentLink.imageUrl || undefined}
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 526b6b5 and f80a6b8.

📒 Files selected for processing (2)
  • apps/dashboard/src/@/api/universal-bridge/links.ts (2 hunks)
  • apps/dashboard/src/app/pay/[id]/page.tsx (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: E2E Tests (pnpm, esbuild)
  • GitHub Check: E2E Tests (pnpm, webpack)
  • GitHub Check: E2E Tests (pnpm, vite)
  • GitHub Check: Size
  • GitHub Check: Lint Packages
  • GitHub Check: Analyze (javascript)
🔇 Additional comments (1)
apps/dashboard/src/@/api/universal-bridge/links.ts (1)

8-9: Successful implementation of type updates for image support.

The PaymentLink type has been properly updated with the renamed property (title instead of label) and the new imageUrl property. Both are correctly marked as optional with the ? operator.

Copy link
Contributor

size-limit report 📦

Path Size Loading time (3g) Running time (snapdragon) Total time
thirdweb (esm) 56.62 KB (0%) 1.2 s (0%) 370 ms (+178.97% 🔺) 1.6 s
thirdweb (cjs) 309.13 KB (0%) 6.2 s (0%) 1.2 s (+3.64% 🔺) 7.4 s
thirdweb (minimal + tree-shaking) 5.69 KB (0%) 114 ms (0%) 122 ms (+1370.39% 🔺) 236 ms
thirdweb/chains (tree-shaking) 531 B (0%) 11 ms (0%) 55 ms (+1477.44% 🔺) 65 ms
thirdweb/react (minimal + tree-shaking) 19.5 KB (0%) 390 ms (0%) 157 ms (+674.33% 🔺) 547 ms

@gregfromstl gregfromstl merged commit 23029db into main May 22, 2025
25 checks passed
@gregfromstl gregfromstl deleted the greg/tool-4583-add-image-to-payment-links branch May 22, 2025 19:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dashboard Involves changes to the Dashboard.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant