KeyValueObjectMapping
KeyValueObjectMapping copied to clipboard
Automatic KeyValue Object Mapping for Objective-C, parse JSON/plist/Dictionary automatically
The logic for looking up an array mapper seems to have a problem if you have multiple array mappers which act on the same key/attribute name (though in different classes)....
This patch allows simple (non-object) arrays at the top level of the JSON data. Previously KVOM assumed that any top-level array was populated with JSON objects - i.e. should be...
The existing code makes the assumption that if mapping an array, the objects in the array are JSON objects, i.e.: ``` [ { "some": "object", "foo":"bar",...}, { "another":"object", "bar":"baz", ......
This fixes https://github.com/dchohfi/KeyValueObjectMapping/issues/92 If you have more than one DCArrayMapping implementation which uses the same key/attribute names, without this patch its pot luck which one you will get at runtime...
In the readme of this github project, we have the following nice and correct example: ``` DCArrayMapping *mapper = [DCArrayMapping mapperForClassElements:[Tweet class] forAttribute:@"tweets" onClass:[User class]]; ``` But on the website...
Is this possible?
I have model with enum property and server returns the string at same property. When I try to parse it fails to convert the same string to enum property. Is...
Automatic KeyValue Object Mapping for Objective-C, parse JSON/plist/Dictionary automatically