improve: [N02] Multiple conditions in a single require statement #256
Conversation
This file contains hidden or 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
## From Audit There is a require statement with multiple conditions in the handleTelepathy function of the Succinct_SpokePool contract. Consider isolating each condition in its own separate require statement with a corresponding error message, to more easily identify the specific condition that failed. ## Developer's response This change allowed me to make unit tests for `Succinct_SpokePool` more strict and check error messages
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.
From Audit
There is a require statement with multiple conditions in the handleTelepathy function of
the Succinct_SpokePool contract.
Consider isolating each condition in its own separate require statement with a corresponding
error message, to more easily identify the specific condition that failed.
Developer's response
This change allowed me to make unit tests for
Succinct_SpokePoolmore strict and check error messages