Closed schmanu closed 1 week ago
β Deploy successful!
Storybook: https://fix_recommended_nonce--walletweb.review.5afe.dev/storybook/
Annotations are provided inline on the Files Changed tab. You can also see all annotations that were generated on the annotations page.
Type | Occurrences | Fixable |
---|---|---|
Errors | 0 | 0 |
Warnings | 0 | 0 |
Ignored | 0 | N/A |
Report generated by eslint-plus-action
This analysis was generated by the Next.js Bundle Analysis action. π€
This PR introduced no changes to the JavaScript bundle! π
St.:grey_question: |
Category | Percentage | Covered / Total |
---|---|---|---|
π‘ | Statements | 78.82% (+0.08% πΌ) |
11346/14394 |
π΄ | Branches | 58.27% (+0.08% πΌ) |
2744/4709 |
π‘ | Functions | 65.79% (+0.07% πΌ) |
1823/2771 |
π’ | Lines | 80.16% (+0.05% πΌ) |
10223/12753 |
1413 tests passing in 195 suites.
Report generated by π§ͺjest coverage report action from 360dec563c17d115bc592d7613476b0a4a936401
Verified
What it solves
Updates
useRecommendedNonce
for 1/1 Safes that execute a transaction directly.How this PR fixes it
Fetched the recommended nonce when the safe's
txHistoryTag
changes. Reason being that 1/1 Safe transactions that get executed immediately never hit the queue and thus do not update thetxQueuedTag
.Adds a unit test for
useRecommendedNonce
How to test it
Checklist