Groot is very useful .But i have a problem！！ about groot HOT 2 CLOSED

Hi @huangqiaobo,

Yes, one of the breaking changes we decided to make for version 1.0 is to make JSON key path mapping explicit: Attributes and relationships that don't have a JSONKeyPath entry are not considered for JSON serialization or deserialization. This makes easier to have other attributes in the managed object that are not related with the JSON (the JSONKeyPath=null solution was a bit contrived).

Unfortunately we couldn't find a good way to make the transition to explicit JSON key paths easier (we are still thinking about it). If this is a big issue for you, I suggest you go back to version 0.2 in the meantime.

You can check the JSONKeyPath documentation for more information.

from groot.

HI @gonzalezreal ，

Thank you for your reply.
I discussed it with my colleagues. At last, I let the groot go back to version 0.2. Because , most of the time , we don't need to change NSManagedObject object back to json in our iOS project. And the attributes name in entity always is the same as in json.

You known, it's troublesome to chosen a name for a property. So, we always use the name in json which get from server, and it is easier to maintenance.

: )

from groot.