fix: set client boundary for Swap and Token components
#1800
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
dschlabach
changed the title
SwapSwap and Token components
alessey
reviewed
Jan 9, 2025
| import { useTheme } from '../../core-react/internal/hooks/useTheme'; | ||
| import { background, cn, pressable, text } from '../../styles/theme'; | ||
| import type { TokenChipReact } from '../types'; | ||
| import { TokenImage } from './TokenImage'; | ||
|
|
||
| /** | ||
| * Small button that display a given token symbol and image. | ||
| * Small button that displays a given token symbol and image. | ||
| * | ||
| * WARNING: This component is under development and | ||
| * may change in the next few weeks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed? Why?
Notes to reviewers
findComponenthas been updated to support RSC payloads from Next. This is only required if the user attempts to composeSwapwith subcomponents (because the children the component receive look slightly different). This is a temporary patch until we migrate to default children.How has it been tested?