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
When using the react sdk and our hooks, I figured that the fact that we have no promise for the getPoolAssetOnDestination for instance, and rather wait for solutions to not be undefined makes it so that if the user changes their input (and hence it changes the params for the api calls) then the solutions will be outdated for the time until the api responds.
Ideally, we should have a reset param that we could call, and that would set the solutions to undefined.
Or we should make sure the solutions is undefined before we do a call to the api, just like we set the loading to true.
What do you think?
The text was updated successfully, but these errors were encountered:
When using the react sdk and our hooks, I figured that the fact that we have no promise for the
getPoolAssetOnDestination
for instance, and rather wait forsolutions
to not beundefined
makes it so that if the user changes their input (and hence it changes the params for the api calls) then thesolutions
will be outdated for the time until theapi
responds.Ideally, we should have a
reset
param that we could call, and that would set thesolutions
toundefined
.Or we should make sure the
solutions
isundefined
before we do a call to the api, just like we set the loading totrue
.What do you think?
The text was updated successfully, but these errors were encountered: