-
Notifications
You must be signed in to change notification settings - Fork 4
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
dApp: Deposit/Withdrawal form improvements - visuals #687
Conversation
✅ Deploy Preview for acre-dapp ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for acre-dapp-testnet ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Removed unused props
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.
dapp/src/components/shared/TokenAmountForm/TokenAmountFormBase.tsx
Outdated
Show resolved
Hide resolved
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.
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.
LGTM, ready for testing 🚀
On the Withdraw form the |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
As per this doc and this Discord discussion, we shouldn't show errors relating to the values entered in the amount input until user clicks Deposit/Withdraw. Right now we're validating the amount dynamically. |
Also, just making sure - the handling of the insufficient balance to handle fee is not in scope of this PR, right? |
It is possible to add suffix to the value. Unfortunately it's impossible to style it so it will be the same color as the value. Ref commit: 8e1f875
Ref commit: 07b172e
Ref commit: a599749
Sorry, I misunderstood the requirements. I reviewed possibilities and applied requested changes basing on Coda write up.
Ref commit: a72361a Added video presentation in the PR description. |
@kpyszkowski I think you missed this one |
Regarding the two items deemed as impossible / hard to implement - I asked @SorinQ about the approach we should take here. Anyway, we can probably close this PR without those changes and handle them in separate tasks (as soon as we resolve all other issues in the current PR). |
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.
Overall it looks good. I left a few small questions. Let me know what you think.
Additionally, I will wait for the merge until tomorrow in case Michalina finds a moment to test. If not, we will do the merge tomorrow.
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.
🚀🚀🚀
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.
Closes: #629
Closes: #652
Closes: #637
Closes: #570
Closes: #630
Changes:
Alert
componentbigIntToUserAmount
instead offixedPointNumberToString
:fixedPointNumberToString
aggressively trims trailing zero values conflicting with the wayNumericFormat
component does it. ThebigIntToUserAmount
seems to fit better hereScreen.Recording.2024-08-19.at.21.57.03.mov