fix: show warning based on trusted flag
#1226
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
iamacook
changed the title
trusted flag
katspaugh
reviewed
Nov 23, 2022
katspaugh
reviewed
Nov 23, 2022
katspaugh
approved these changes
Nov 23, 2022
ESLint Summary View Full Report
Report generated by eslint-plus-action |
Branch preview |
Merged
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.
What it solves
Resolves default warning when no signatures exist.
How this PR fixes it
A warning should no longer shown by default when no signatures are present, e.g. when queuing an approval of a nested Safe. Instead, they are shown when the
trustedflag isfalse.Note: no warning will be shown until the flag is implemented.
How to test it
Open an "untrusted" transaction and observe the warning