Open jfschwarz opened 1 week ago
β Deploy successful!
Storybook: https://role_multisend_fix--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. π€
Page | Size (compressed) |
---|---|
global |
1000.1Β KB (-1Β B) |
The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.
Any third party scripts you have added directly to your app using the <script>
tag are not accounted for in this analysis
If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!
[!CAUTION] Test run failed
St.:grey_question: |
Category | Percentage | Covered / Total |
---|---|---|---|
π‘ | Statements | 78.79% (-0.01% π») |
11440/14520 |
π΄ | Branches | 58.24% (+0.12% πΌ) |
2789/4789 |
π‘ | Functions | 65.8% (+0.02% πΌ) |
1837/2792 |
π’ | Lines | 80.16% (-0.02% π») |
10306/12857 |
Report generated by π§ͺjest coverage report action from 6655d398c6c4e323c59da640aa3b96b5ff9efd61
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
Taking into account the feedback points from design & QA, this PR improves the integration of role-based access control into the execution flow previously delivered with #3768.
Integrate into the main "execute or sign" card
Previously we've integrated the execution through a role as new card appearing above the default "execute or sign" card. As suggested by the wallet design team, we've now improved the user experience by enabling the execution through a role directly from the default form.
Call is allowed for the role:
Call is not allowed:
Logic: default execution as owner vs execution as role member
Handle edge cases with batch transactions
So far we didn't correctly handle cases where the Role mod expects a different multi-send address than the one used per default in Safe Wallet. This PR fixes it through a lookup of the multi-send address configured on the Roles mod and routing the batch transaction accordingly.
More user-friendly error messages for failing permission checks
Review the complete list of potential messages here.