-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
KZCall on different object? #41
Comments
For global/shared support I'd use boxing not KZCall, Adding boxValueAsGroup: as a category on KZPM and then use KZBox(Group, property) Readme should have an example about that, does that approach seem better? Krzysztof Zabłocki On Mon, Nov 3, 2014 at 5:21 PM, Kevin Renskers [email protected]
|
Well, it would at least make it global and reusable, but it would still mean duplicating a method to a boxing method. It's not ideal. Something like |
Should be straight forward, we'd probably need to add KZCallClass or similar because target and called will differ then Krzysztof Zabłocki On Mon, Nov 3, 2014 at 5:31 PM, Kevin Renskers [email protected]
|
+1 KZCallClass would be great! |
Let's say I have an User object, and an user belongs to a group.
Now, what I'd like to be able to do is something like this:
So, call
[Group groupWithDict:dict]
and save that result toself.group
. However, I now constantly have to create an intermediary helper method on the object I'm parsing, so the user object now gets something like this:After writing a bunch of classes like this, it gets really tedious to duplicate these methods like this. Is there any solution? It looked like
KZCallT
would be handy, but the property then needs to be on the target object instead of self.The text was updated successfully, but these errors were encountered: