feat: Adding context to get current confirmation PR-4#26649
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 [d7f6945]
Page Load Metrics (90 ± 12 ms)
Bundle size diffs [🚀 Bundle size reduced!]
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #26649 +/- ##
===========================================
+ Coverage 70.12% 70.13% +0.01%
===========================================
Files 1423 1424 +1
Lines 49539 49568 +29
Branches 13864 13868 +4
===========================================
+ Hits 34736 34763 +27
- Misses 14803 14805 +2 ☔ View full report in Codecov by Sentry. |
digiwand
left a comment
There was a problem hiding this comment.
Nice work! minor TS suggesiton to remove as unknown
ui/pages/confirmations/hooks/useCurrentSignatureSecurityAlertResponse.test.ts
Outdated
Show resolved
Hide resolved
Builds ready [0c90ccb]
Page Load Metrics (1745 ± 139 ms)
Bundle size diffs
|
Builds ready [dbf1d1c]
Page Load Metrics (1485 ± 47 ms)
Bundle size diffs
|
|
Builds ready [710b825]
Page Load Metrics (1778 ± 50 ms)
Bundle size diffs
|
| }; | ||
|
|
||
| if (!currentConfirmation?.msgParams) { | ||
| if (!(currentConfirmation as SignatureRequestType)?.msgParams) { |
There was a problem hiding this comment.
Nit: This type may not be needed given it's already used above
There was a problem hiding this comment.
good point this is indeed not needed, I will fix this in following PR



Description
Using context to get currently selected confirmation in re-designed confirmation pages. This is done to switch to using react context transient UI state in re-designed confirmation pages.
Related issues
Ref: #26414
Manual testing steps
NA
Screenshots/Recordings
NA
Pre-merge author checklist
Pre-merge reviewer checklist