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
The max-payment field has a validation not to accept amounts above a "max" filter. But if the payment is set, and then the max-paymnet is lowered, the payment requested will be above the new "max" value. We need to improve validation in that case.
I tried different methods according to the quasar-input validation, but it looks like it's going to need more time invested to fix it. But validation needs to happen also on the chain side,
The max-payment field has a validation not to accept amounts above a "max" filter. But if the payment is set, and then the max-paymnet is lowered, the payment requested will be above the new "max" value. We need to improve validation in that case.
I tried different methods according to the quasar-input validation, but it looks like it's going to need more time invested to fix it. But validation needs to happen also on the chain side,
The text was updated successfully, but these errors were encountered: