You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All numerical token balance inputs should have a 'max' button applied to them.
In some instances, people may want to deposit/withdraw the entire balance of a certain token in Finance (eg. performing the Sai to Dai migration).
Having a 'max amount' button (as almost all exchanges do to create orders or withdraw funds) is useful not only to prevent mistakes (see image below) but also to allow to wipe the balance of a certain token down to the last decimal (which we don't show in the UI).
The text was updated successfully, but these errors were encountered:
Hi, I'm new here 😄 , I would like to fix this issue to know the project.
If I understand the architecture, the pull request is in aragon/aragon-apps repository.
The task consists of adding a button on all numerical token balance inputs to select max amount available. The change affects apps agent, finance and token manager.
Is there any design? or could it be something like this?
I should assign me the issue or something like that or it's not necessary.
If I understand the architecture, the pull request is in aragon/aragon-apps repository.
The task consists of adding a button on all numerical token balance inputs to select max amount available. The change affects apps agent, finance and token manager.
Yes, that is correct!
I should assign me the issue or something like that or it's not necessary.
All numerical token balance inputs should have a 'max' button applied to them.
In some instances, people may want to deposit/withdraw the entire balance of a certain token in Finance (eg. performing the Sai to Dai migration).
Having a 'max amount' button (as almost all exchanges do to create orders or withdraw funds) is useful not only to prevent mistakes (see image below) but also to allow to wipe the balance of a certain token down to the last decimal (which we don't show in the UI).
The text was updated successfully, but these errors were encountered: