-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add SuspiciousMessageMode
detector
#193
Add SuspiciousMessageMode
detector
#193
Conversation
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.
Great work! Let's fix the corner case and a few minor code style issues.
We also need to update the CHANGELOG |
Refactor: add comments to new detector and change logic
case "method_call": | ||
warnings.push( | ||
this.makeWarning( | ||
"Function calls should not be used in mode expression; use symbolic constants instead", |
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.
Why? It seems valid to me to write a function or a method that evaluates the send parameters based on some contract's state.
Let's also bump the number of detectors in |
fix: Made valid to write a function or a method that evaluates the send parameters. chore: update numbers detectors in Readme
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.
LFG. Thank you!
Closes #85
CHANGELOG.md
yarn test-all