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
For some FE widgets, like transfer and swap, if the backend happens to return a widget command with invalid inputs, it would be good if the FE can detect and warn.
For example, if I type "transfer" in the current dev, the BE returns this <|display-transfer(token,amount,address)|>, we will get the following error:
We'll be trying hard on the BE not to have such widgets be returned, but it is hard to guarantee, and it would also be good if the FE client didn't become stuck when something invalid does come up.
In the old code, I started adding something like the following to guard against unrecognized tokens, but this doesn't handle non-numeric amounts or invalid address strings, etc. And also the new code looks different so wasn't able to easily find how to add these equivalently.
For some FE widgets, like transfer and swap, if the backend happens to return a widget command with invalid inputs, it would be good if the FE can detect and warn.
For example, if I type "transfer" in the current dev, the BE returns this
<|display-transfer(token,amount,address)|>
, we will get the following error:We'll be trying hard on the BE not to have such widgets be returned, but it is hard to guarantee, and it would also be good if the FE client didn't become stuck when something invalid does come up.
In the old code, I started adding something like the following to guard against unrecognized tokens, but this doesn't handle non-numeric amounts or invalid address strings, etc. And also the new code looks different so wasn't able to easily find how to add these equivalently.
The text was updated successfully, but these errors were encountered: