fix: show chain selector for single-chain apps - #2698
ayaanoncrypto wants to merge 2 commits into
Conversation
|
Someone is attempting to deploy a commit to the rainbowdotme Team on Vercel. A member of the Team first needs to authorize it. |
馃 Changeset detectedLatest commit: e2fbddf The changes in this PR will be included in the next version bump. This PR includes changesets to release 18 packages
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 |
There was a problem hiding this comment.
馃挕 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 97ebd86e41
鈩癸笍 About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 馃憤.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| {ready && account && connectionStatus === 'connected' ? ( | ||
| <> | ||
| {chain && (chains.length > 1 || unsupportedChain) && ( | ||
| {chain && ( |
There was a problem hiding this comment.
Add a changeset for the ConnectButton behavior change
This alters user-facing behavior in the published @rainbow-me/rainbowkit package, but the commit includes no .changeset entry. Without a patch changeset, the release workflow will not record or version this fix for consumers; add one covering the core package.
AGENTS.md reference: AGENTS.md:L99-L104
Useful? React with 馃憤聽/ 馃憥.
Summary
Closes #1418.
Render the current chain selector whenever a connected account has chain data. Single-chain applications now show the active chain in the Connect Button, matching multi-chain and unsupported-chain behavior.
Testing
git diff --checkpassed.