Rule "Literal string for key path" does not handle ignore option for valueForKeyPath
Issue #59
closed
When configuring the rule "Literal string for key path" (LiteralStringKeyPath), there is an option to ignore valueForKey and setValue:forKey: for collections. However, this does not handle valueForKeyPath and setValue:forKeyPath and thus creates issues in these cases.
Comments (2)
-
repo owner -
repo owner - changed status to closed
Fixed in v1.4.
- Log in to comment
Thanks for reporting this. A fix for this will be included in the next release.