-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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: upgrade transaction controller to get incoming transactions using accounts API #12419
Conversation
Include network client ID in addTransaction calls. Include network client ID in updateIncomingTransactions calls. Include network client Id in getNetworkNonce calls. Update calls to wipeTransactions. Create global network utils. Move getGlobalEthQuery to global network utils. Add network client ID to test data.
Fix Yarn duplication.
Fix linting.
Remove usage of Etherscan constants. Update notification to handle new event.
Bitrise❌❌❌ Commit hash: 6e7d2e0 Note
Tip
|
Bitrise❌❌❌ Commit hash: 77e1f90 Note
Tip
|
Bitrise❌❌❌ Commit hash: 3d85274 Note
Tip
|
Bitrise❌❌❌ Commit hash: 9225952 Note
Tip
|
Bitrise❌❌❌ Commit hash: 687abdc Note
Tip
|
Bitrise✅✅✅ Commit hash: b9d4e82 Note
|
Quality Gate failedFailed conditions |
Assets changes LGTM! Thnx! |
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.
LGTM! For we can move quicker, we can address the lack of coverage in a follow up PR
Description
Update
@metamask/transaction-controller
to retrieve incoming transactions using the accounts API rather than Etherscan.Add incoming transaction E2E tests.
Related issues
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist