-
Notifications
You must be signed in to change notification settings - Fork 1k
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
objectForMapping not called #546
Comments
objectForMapping(map: Map) was moved into Replace Mappable with StaticMappable wherever you need to use objectForMapping |
Thanks @jpstern |
I also ran into this recently and it took some time to debug. I would have much preferred this to come with a version 2.0 ObjectMapper since this was a breaking change. Is there a particular reason it wasn't? |
@jakecraige my mistake, this change definitely warranted a major version number change. |
Hello guys.
I've updated pods (ObjectMapper (1.4.0)) a moment ago and had found out that
func objectForMapping(map: Map)
not called anymore when I callParsingService<NSManagedObjectInheritant>().parseObject(Object)
.It causes objects being duplicated. Please advise if I should use other function now.
UPD: Installed version 1.3. It works fine.
The text was updated successfully, but these errors were encountered: