-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
feat: cross chain swaps - tx status - UI #28657
base: develop
Are you sure you want to change the base?
Conversation
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
Builds ready [3f3864f]
Page Load Metrics (1976 ± 63 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
3f3864f
to
e522a06
Compare
Builds ready [74b114e]
Page Load Metrics (1933 ± 118 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
Builds ready [47a8853]
Page Load Metrics (2138 ± 114 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
Builds ready [ac773b7]
Page Load Metrics (1893 ± 85 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
<!-- Please submit this PR as a draft initially. Do not mark it as "Ready for review" until the template has been completely filled out, and PR status checks have passed at least once. --> ## **Description** <!-- Write a short description of the changes included in this pull request, also include relevant motivation and context. Have in mind the following questions: 1. What is the reason for the change? 2. What is the improvement/solution? --> This PR is a collection of all the background related code from #27740 (no UI changes). It has been split up in order to make it easier to review. A follow up PR containing all the UI changes from #27740 is here: #28657 The main addition is the `BridgeStatusController` and its supporting code. If you would like to test the functionality of this PR through the UI, please do so through #27740. [![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/28636?quickstart=1) ## **Related issues** Branched off from #27740 ## **Manual testing steps** Refer to #27740 ## **Screenshots/Recordings** Refer to #27740 ## **Pre-merge author checklist** - [ ] I've followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Extension Coding Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md). - [ ] I've completed the PR template to the best of my ability - [ ] I’ve included tests if applicable - [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.
ac773b7
to
98cd8d4
Compare
Builds ready [569b06f]
Page Load Metrics (1778 ± 93 ms)
|
I'm noticing an issue where I'm seeing the transaction pending on both the Lifi and socket explorers but it's returning pending in the UI and LiFi because of dest transaction despite the transaction being complete https://www.loom.com/share/f66dec23c63b4353aa289a2723e3d984 It does look like it was executed through lifi based on the calldata for the transaction. So seems like it may just be an issue on Lifi side Update: once Lifi was correctly resolving the transaction status, I could see the bridge showing up correctly in the UI |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apart from some edge cases I'm seeing here, the polling and status fetching seems to work correctly
So is the issue here that the MM UI is not updating fast enough given that the Socket Explorer said that both source + dest txs were confirmed? |
0077794
569b06f
to
0077794
Compare
Builds ready [b44c49f]
Page Load Metrics (1910 ± 83 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
Most of the UI functions pretty well but I never get a quote or am able to execute the bridge: Screen.Recording.2024-11-27.at.4.59.25.PM.mov |
Spoke to the team, the UI for "no quotes received" is still in development. |
Description
This PR is a collection of all the UI related code from #27740 (no UI changes). It has been split up in order to make it easier to review.
The main addition is the Bridge Transaction Details and its supporting code.
Related issues
Related to #27740, #28636
Manual testing steps
Add
BRIDGE_USE_DEV_APIS=1
to.metamaskrc
to enable BridgeRefer to to #27740
Screenshots/Recordings
Refer to to #27740
Pre-merge author checklist
Pre-merge reviewer checklist