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.
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
fix(contracts-rfq): limit the amount of solhint warnings [SLT-245] #3182
fix(contracts-rfq): limit the amount of solhint warnings [SLT-245] #3182
Changes from all commits
0e1bfa2
e462eff
4796b36
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
Consider adding parameters to some errors for more detailed reporting.
The error definitions are clear and well-organized. However, some errors could benefit from additional context. For example:
This would provide more specific information when these errors occur, aiding in debugging and improving the developer experience.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codebase verification
Unused IFastBridgeV2Errors in FastBridgeV2Test
No instances of
IFastBridgeV2Errors
usage found withinFastBridgeV2.t.sol
beyond its inclusion in the contract inheritance and import statements.Consider removing
IFastBridgeV2Errors
from the inheritance if it is not utilized, or ensure that it is appropriately used to enhance error handling in the test cases.🔗 Analysis chain
LGTM: Contract signature updated to include IFastBridgeV2Errors.
The
FastBridgeV2Test
contract now inherits from bothTest
andIFastBridgeV2Errors
, which is consistent with the new import statement. This change should improve error handling and testing capabilities, aligning with the PR's objective of enhancing code quality.To ensure this change doesn't introduce any unintended side effects, please verify:
IFastBridgeV2Errors
are properly used in the test cases.Test
andIFastBridgeV2Errors
.You can use the following script to check for the usage of error types:
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
Length of output: 133
Script:
Length of output: 95
Script:
Length of output: 233