-
Notifications
You must be signed in to change notification settings - Fork 5k
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
feat: improve xchain swaps slippage settings with decimals and warnings #29617
base: main
Are you sure you want to change the base?
Conversation
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
Builds ready [25483db]
Page Load Metrics (1627 ± 64 ms)
Bundle size diffs
|
Builds ready [a557648]
Page Load Metrics (1724 ± 46 ms)
Bundle size diffs
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Worked for decimal separator as a period.
Does this work for languages where the decimal separator is a comma?
EDIT: nvm, seems like MM keeps commas for tokens like ETH, and percentage values
EDIT2: eh sometimes ETH is comma separated, sometimes not
Builds ready [3b07d96]
Page Load Metrics (1763 ± 74 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
Builds ready [d6d1448]
Page Load Metrics (1995 ± 95 ms)
Bundle size diffs
|
Description
The slippage settings for xchain transactions was not allowing users to input a decimal (i.e. 0.5%), only whole numbers (0, 1, so on...). It also did not display a warning for low slippage settings. This addresses both by allowing the user to input decimal numbers, and displaying a warning when the custom slippage is set to <0.5% in the settings modal.
Related issues
Fixes: https://consensyssoftware.atlassian.net/browse/MMS-1830
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist