Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

allow multi-level key paths for relationship mappedKeyName #280

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
2 participants

cmezak commented Oct 15, 2012

I had the impression from Saul's blog post that mappedKeyName could be a full key path, not just a key, but valueForKey: is being used in MR_setRelationships:forKeysWithObject:withBlock:. Switched to valueForKeyPath:.

This allows you to actually use a multi-level key path for mappedKeyName for a relationship.

using valueForKeyPath: instead of valueForKey for pulling relationshi…
…p object data from import data

This allows you to actually use a multi-level key path for mappedKeyName for a relationship.

@cmezak cmezak closed this Oct 15, 2012

Owner

casademora commented Oct 15, 2012

Not sure Matt Long wrote that blog post ;)

cmezak commented Oct 16, 2012

Brain fail. Sorry, Saul, and thanks for the post! :P

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment