feat(checkout-widgets): Include token address and amount in bridge risk assessments #2696
Conversation
This file contains hidden or 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
|
View your CI Pipeline Execution ↗ for commit 3d4cc00
☁️ Nx Cloud last updated this comment at |
allan-almeida-imtbl
previously approved these changes
Sep 5, 2025
| }); | ||
|
|
||
| // Use child token address if mapping exists, otherwise use original token address | ||
| tokenAddress = tokenMapping.childToken ?? formToken.token.address; |
There was a problem hiding this comment.
is this fallback necessary if you already assign
let tokenAddress = formToken.token.address;
above the trycatch?
keithbro-imx
reviewed
Sep 5, 2025
packages/checkout/widgets-lib/src/widgets/bridge/components/BridgeForm.tsx
Outdated
Show resolved
Hide resolved
keithbro-imx
approved these changes
Sep 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Hi👋, please ensure the PR title follows the below standards:
type(scope): message. For example:feat(passport): my new feature!after thetype(scope), for examplefeat(passport)!: my new breaking featureSummary
Detail and impact of the change
Added
Changed
Deprecated
Removed
Fixed
Security
Anything else worth calling out?