feat: update types and checks for multisigs #2693
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Jest Unit tests resultsDuration: 61.148 seconds
Outcome: Passed | Total Tests: 743 | Passed: 742 | Failed: 0
|
tuul-wq
approved these changes
Nov 21, 2024
johnthecat
approved these changes
Nov 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update types and checks for flexible multisig
Potentially, there're more places where checking for flexibleMultisig will be required as well
Check functions update:
previous
isMultisig->isRegularMultisigisMultisigAccount->isRegularMultisigAccountisMultisigandisMultisigAccountare used now to check if it's a multisig in general (flexible or regular)