LiteralStringKeyPath is triggered for Core Animation Key-Value Coding Extensions (no easy solution here)
Issue #56
closed
There aren't any selectors available for these keys/key paths, so we can't fix this rule by doing the usual NSStringFromSelector(@selector(keyPath))
.
Core Animation Key-Value Coding Extensions
Example case that would trigger this warning:
[CABasicAnimation animationWithKeyPath:@"transform.translation.x"];
I think a good solution for this rule would be to ignore key paths that contain keys from the Core Animation Key-Value Coding Extensions.
Comments (5)
-
-
Thanks for reporting this. A fix will be included in the next release.
-
Awesome. Thanks!
-
- changed status to resolved
Fixed in v1.3
-
- changed status to closed
- Log in to comment
This is also triggered in similar cases for uses of UIMotionEffect and its subclasses