Skip to content
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

Display loading component in exchange operations #21

Merged
merged 7 commits into from
Apr 14, 2020
Merged

Display loading component in exchange operations #21

merged 7 commits into from
Apr 14, 2020

Conversation

patitonar
Copy link
Contributor

Relates to #6

This PR updates the exchange plugin to display a Loading component (similar to transfer operations) when exchanging assets.

I added a custom loading message property to the Pairs. It is useful especially for pairs that use a bridge, so the user can be properly informed that it requires some time to finish the operation.

Also, I refactored the XDaiBridge component, to extract the common functionality of bridges to a separate Bridge class, so new bridges pairs can be added easily.

Finally, the bridge exchange operations were updated to resolve when the asset from the other network is transferred to the user instead of when the transaction of the user is mined. This allows displaying the Loading component all the time until the assets are relayed by the bridge.

bridgeLoading

Copy link
Collaborator

@dmihal dmihal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! I like that you've turned the XDaiBridge into a more generic bridge.

packages/exchange/src/pairs/Bridge.ts Outdated Show resolved Hide resolved
packages/exchange/src/pairs/XDaiBridge.ts Outdated Show resolved Hide resolved
packages/exchange/src/pairs/XDaiBridge.ts Outdated Show resolved Hide resolved
@dmihal dmihal merged commit fc1e8b0 into burner-wallet:develop Apr 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants