[SDK] Fix: Apply accentButtonText theme key to the Spinner inside of PayEmbed Buttons

[RobbyUitbeijerse]

Various components in the codebase were a spinner was rendered inside a button, the accentButtonText key was applied to the spinner. This seems to make a bit more sense compared to using accentText which will make it hard to give the button a light color while keeping the rest dark, since the spinner color is related to the accentText rather than the button text colour.

Attached is a situation I was running into:

Changing the theme key that's applied to be accentTextButton throughout all components rendered inside of a makes things nice and consistent, and resolves the above scenario.

---

PR-Codex overview

This PR focuses on fixing the theme color of the loading spinner in the PayEmbed component to enhance visual consistency.

Detailed summary

• Updated the color prop of the <Spinner> component in FiatScreenContent.tsx from accentText to accentButtonText.
• Updated the color prop of the <Spinner> component in SwapScreenContent.tsx from accentText to accentButtonText.

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

Summary by CodeRabbit

• Style
  • Updated the loading spinner color on the fiat and swap screens for improved visual consistency.
  • Fixed the loading spinner color in the payment embed component for better theme alignment.

[changeset-bot]

🦋 Changeset detected

Latest commit: 4ab3604

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

[graphite-app]

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.

[coderabbitai]

Walkthrough

The changes update the color prop for Spinner components within loading states in two UI files. Specifically, the Spinner color changes from "accentText" to "accentButtonText" in both the fiat and swap quote screens. No other logic, control flow, or public interfaces are modified.

Changes

File(s)	Change Summary
.../ConnectWallet/screens/Buy/fiat/FiatScreenContent.tsx .../ConnectWallet/screens/Buy/swap/SwapScreenContent.tsx	Updated Spinner color prop from "accentText" to "accentButtonText" in loading states.
.changeset/slick-apes-do.md	Added patch note describing fix to theme color of loading spinner in PayEmbed component.

Sequence Diagram(s)

No sequence diagram is generated as the changes are limited to UI color props and do not affect control flow or feature logic.

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.

---

📜 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 29e272a and 4ab3604.

📒 Files selected for processing (1)

• .changeset/slick-apes-do.md (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• .changeset/slick-apes-do.md

---

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

[vercel]

@RobbyUitbeijerse is attempting to deploy a commit to the thirdweb Team on Vercel.

A member of the Team first needs to authorize it.

[joaquim-verges]

thank you!