You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because the methods declared in a category are added to an existing class, you need to be very careful about method names.
If the name of a method declared in a category is the same as a method in the original class, or a method in another category on the same class (or even a superclass), the behavior is undefined as to which method implementation is used at runtime.
Provide several examples of what would and wouldn't trigger violations.
// should triggerextensionFoo{overridevarbar:String{return""}overridefunc baz(){}}
Should the rule be configurable, if so what parameters should be configurable?
Just severity.
Should the rule be opt-in or enabled by default? Why?
See README.md for guidelines on when to mark a rule as opt-in.
I think it should be enabled by default, but I'm afraid that this might cause a lot of violations that are not easily fixed.
I have an initial implementation for this already, I just need some time to clean it up.
The text was updated successfully, but these errors were encountered:
New Issue Checklist
Rule Request
the community thinks about this.
Adding
override
for Swift-only declarations is already not possible. It's only possible for@objc
declarations.From Apple's Programming with Objective-C
Just severity.
See README.md for guidelines on when to mark a rule as opt-in.
I think it should be enabled by default, but I'm afraid that this might cause a lot of violations that are not easily fixed.
I have an initial implementation for this already, I just need some time to clean it up.
The text was updated successfully, but these errors were encountered: