Skip to content
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

chore: add some exclude options for slither #6

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

snowwhitedev
Copy link

No description provided.

@@ -1,4 +1,4 @@
{
"detectors_to_exclude": "block-timestamp",
"detectors_to_exclude": "block-timestamp, reentrancy-events, solc-version",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, @snowwhitedev , could you explain, why do you want to disable those detectors?
I think its OK to get notifications about potential "reentrancy-events" and disable warnings with commenting. (I understand that reentrancy-events works buggy and sometimes false detects)
solc-version can be helpful too to keep compiler fresh. Isn't it?

Tell me please, your reasons.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @oleggrib
Regarding reentrancy-events, slither even though we took count the case. I faced this several times when I used slither in my local. For example you can see this. #5 (comment)

Regarding solc-version, in most cases we are using dependencies such as openzepplin-contracts when writing smart contract. They includes several solidity versions, so slither shows warning or error message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants