fix: use transactionMeta for TransactionController events#24003
fix: use transactionMeta for TransactionController events#24003
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. |
There was a problem hiding this comment.
Is there a way to test that the _onUserOperationTransactionUpdated function does what it is expected to do?
The _ suggests that it's intended as private function and we don't usually add tests for private functions directly, but perhaps we could test that the transaction-updated event is handled properly?
|
I must say that I don't really know 😅 We did a small investigation with @montelaidev and we found out what was this error. We were doing manual tests though... I don't know if the e2e tests should cover this one (implicitly)... Any thought regarding the best approach to test this @matthewwalsh0? |
montelaidev
left a comment
There was a problem hiding this comment.
Tested with @ccharly
d2c84b7 to
d69b91c
Compare
Builds ready [d69b91c]
Page Load Metrics (818 ± 551 ms)
Bundle size diffs [🚀 Bundle size reduced!]
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #24003 +/- ##
========================================
Coverage 67.28% 67.28%
========================================
Files 1275 1275
Lines 49707 49707
Branches 12916 12916
========================================
Hits 33444 33444
Misses 16263 16263 ☔ View full report in Codecov by Sentry. |
Builds ready [f06f660]
Page Load Metrics (1675 ± 830 ms)
Bundle size diffs [🚀 Bundle size reduced!]
|
|
Testing on Chrome Version 125.0.6422.61 with the Flask build linked here ❌ The extension shows a forever loading screen when I go to try and send funds from my 4337 Account back to my main EOA account. Screen.Recording.2024-05-21.at.1.24.40.PM.mov |
|
Using Flask build 12.0.0 046766c1 Testing on Chrome Version 126.0.6478.57 ✅ pr-24003-chrome-validation.mov |
Description
Use of a wrong field name which ends up as an error once published.
Related issues
Fixes: https://github.com/MetaMask/accounts-planning/issues/359
Manual testing steps
EIP_4337_ENTRYPOINTin your.metamaskrcorbuilds.yml(or he might already be up-to-date)Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist