galacticcouncil/Basilisk-ui-old

Bug: if I start to place numbers in the token when try to add liquidity, it does not take the order

Closed this issue · 1 comments

if I start to place numbers in the token B, when i will add liquidty to pools, it does not take the order.

Description

when trying to add liquidity, starting with token B, token A is not filled, even the problem "insufficient liquidity in token A" appears

Expected Behaviuor

fill in the numbers of token b, and therefore its equivalent in Token A, for greater ease in adding liquidity (if the token with the lowest balance is in position b)

Actual Behaviuor

It does not put the equivalent in token A, and I get the error "insufficient liquidity of token A)

Possible Fix
X

Steps to Reproduce

Go to pools
Enter any amount on token B first
Submit

User is able to do this action with all the pools, the matter is start on token B

Context

I tried to add liquidity starting with token B, because it was easier to calculate based on that asset

Screenshot_44
Screenshot_45
Screenshot_46
the order should not matter

@jrafaelangarita For now there is validation in place
image
The whole new UX for this screen is in progress.