-
Notifications
You must be signed in to change notification settings - Fork 285
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
The max-public-structs
rule starts finding many false positives in version 1.5.0
#1103
Labels
Comments
1 task
Hi @zak-pawel thanks for reporting the issue. I'll check what is happening (BTW, the failure message does not help in knowing what is the actual limit the linter is checking 👎 ) |
chavacava
added a commit
that referenced
this issue
Nov 11, 2024
chavacava
pushed a commit
that referenced
this issue
Nov 12, 2024
This was referenced Nov 13, 2024
chavacava
added a commit
that referenced
this issue
Nov 15, 2024
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The
max-public-structs
rule starts finding many false positives in version1.5.0
.Version
1.4.0
, with the same configuration, doesn't find any findings.I will demonstrate this using the repository https://github.com/influxdata/telegraf (over 650k lines) as an example.
To Reproduce
Steps to reproduce the behavior:
go install github.com/mgechev/revive@latest
632
false positives.Expected behavior
I would like there to be no findings for the given repo, branch and configuration - just as it was for the previous version of
revive
(1.4.0
)."Logs
All findings attached:
revive_1.5.0_findings_for_telegraf.txt
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: