-
Notifications
You must be signed in to change notification settings - Fork 408
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
refactor: SignOrExecute
elements
#1842
Conversation
* Refactor: extract SignOrExecute logic into hooks * isExecutionLoop * Fix isExecutionLoop * Add hook tests * PR comments * Create asserts * Use isValidMasterCopy * Track relayed executions * Tests
* Refactor: move getRemainingRelays to a service * Rename relaying service and constants
Branch preview✅ Deploy successful! |
ESLint Summary View Full Report
Report generated by eslint-plus-action |
* refactor: address relaying review comments * fix: revert type error expectation * fix: add help article link * fix: spelling mistake
Screen.Recording.2023-04-19.at.14.36.18.movSteps for the tx creation:
|
Looks like @liliya-soroka can you provide the steps in how you created that transaction? |
@usame-algan , added to the comment with the issue |
@liliya-soroka I was able to reproduce the bug on dev as well. I suggest to fix it there first. Will create an issue for it. |
What was tested:
|
What it solves
Part of #1828
An umbrella PR for code refactors in preparation for a tx flow redesign.
How to test
Make all kinds of transactions, immediate executions/signatures/on-chain signatures/relayed executions. Everything should work like before.
Analytics changes
Relayed executions now have their own event instead of "Propose".