-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
[Swift 4.1] Add redundant_set_access_control rule #2036
Conversation
Generated by 🚫 Danger |
Codecov Report
@@ Coverage Diff @@
## master #2036 +/- ##
=========================================
Coverage ? 89.63%
=========================================
Files ? 257
Lines ? 14924
Branches ? 973
=========================================
Hits ? 13377
Misses ? 1529
Partials ? 18
Continue to review full report at Codecov.
|
This is ready for review! It looks a huge PR, but most of the changes are in Rules.md. |
Fixes #1869
The more important thing here is not the rule itself, but we have to make a decision on how we're going to mark rules that won't work on older Swift compiler versions, as Swift 4.1 includes some SourceKit fixes and improvements that will provide us more information to create rules.
We also probably should hold merging this until we have CI running Swift 4.1. I just wanted to open the PR to get feedback on the
minSwiftVersion
approach.I also didn't implement auto correct on purpose: I think this rule shouldn't be triggered frequently and when there're violations, the user should check whether the correct behavior would be actually use the same ACL for the setter or it was a mistake in the first place.