This repository was archived by the owner on Sep 12, 2018. It is now read-only.
Adds keypath mapping support #98
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ct context. Exposed new methods passing a context as additional parameter.
…of deepness. Fixes supermarin#60 with error message 'to-many key not allowed here'
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By optionally returning +keyPathForRemoteKey: in any NSManagedObject subclass, it checks for a keypath related to the remote key, to be able to call -valueForKeyPath: instead of -objectForKey:
This allows keypaths mappings, for objects that don't need to be nested in CoreData but come nested from the remote payload.
It may still need: