-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sign and send in extension is broken #244
Comments
cc @thomaseizinger: this could have something todo with your refactoring. |
Interesting. This isn't covered by the tests then? On that front: We don't have proper routing in the extension yet. Would be a good thing to add. The current state keeping and decision making what is being rendered is error prone as we can see. |
The test only covers that the signing and sending (i.e. the swap) was successful. It stops afterwards :) |
Floating promises make awaiting a function useless because the promise is just executed in the background and the function returns immediately. In our case, this led to the onSuccess() handler in the ConfirmSwap component being called too early and hence the page refreshed at a point where the old state (i.e. the swap to sign) was still present. Fixes comit-network#244.
Floating promises make awaiting a function useless because the promise is just executed in the background and the function returns immediately. In our case, this led to the onSuccess() handler in the ConfirmSwap component being called too early and hence the page refreshed at a point where the old state (i.e. the swap to sign) was still present. Fixes comit-network#244.
We have the following flow if a user wants to trade against bobtimus:
Trade
tab.Sign and Send
/swapped/tx/123e41....
At the moment step 5 is broken, i.e. the user stays on the
Sign and Send
page. Signing works and the web app gets redirected.The text was updated successfully, but these errors were encountered: