Skip to content
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: limit UI upgrade 2 - USD precision #5274

Merged

Conversation

alfetopito
Copy link
Collaborator

@alfetopito alfetopito commented Jan 9, 2025

Summary

  • Fix max precision bug with USD amounts
  • Attempt fixing issues with precision

To Test

  1. On limit, turn on global USD
  2. On a sell token which you have balance, click on max
  3. Place a fill or kill order
  • Should NOT show insufficient balance

  • Should use ALL available balance

  • USD amounts should be a bit less finicky (better with rounding)

Copy link

vercel bot commented Jan 9, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
cowfi 🔄 Building (Inspect) Visit Preview Jan 10, 2025 4:34pm
explorer-dev 🔄 Building (Inspect) Visit Preview Jan 10, 2025 4:34pm
sdk-tools 🔄 Building (Inspect) Visit Preview Jan 10, 2025 4:34pm
swap-dev 🔄 Building (Inspect) Visit Preview Jan 10, 2025 4:34pm
widget-configurator 🔄 Building (Inspect) Visit Preview Jan 10, 2025 4:34pm
1 Skipped Deployment
Name Status Preview Updated (UTC)
cosmos ⬜️ Ignored (Inspect) Visit Preview Jan 10, 2025 4:34pm

@alfetopito alfetopito force-pushed the feat/limit-ui-upgrade-2_price-precision branch from 6524adc to 794114d Compare January 10, 2025 16:33
@alfetopito alfetopito merged commit f3a57ae into feat/limit-ui-upgrade-2 Jan 10, 2025
5 of 11 checks passed
@alfetopito alfetopito deleted the feat/limit-ui-upgrade-2_price-precision branch January 10, 2025 16:34
@github-actions github-actions bot locked and limited conversation to collaborators Jan 10, 2025
@@ -18,7 +18,7 @@ export enum LimitOrderDeadlinePreset {
ONE_DAY = '1 Day',
THREE_DAYS = '3 Days',
ONE_MONTH = '1 Month',
SIX_MONTHS = '6 Months (max)',
SIX_MONTHS = '1 Year (max)',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alfetopito was this intentional?

I thought it was changed already, and also now it doesn't match te const name and the label

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes!
I believe @fairlighteth did some refactoring where the label was reverted back to an earlier version.
Great catch that I forgot to update the label 🤦

#5282

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants