You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I do not have an explicit id field in any of my core data entities, but I would like to have a unique identifier for serialization -- in my application I use the NSManagedObject objectID property as the unique identifier, is it possible to have Groot serialize it along with the rest of my fields?
The text was updated successfully, but these errors were encountered:
this would be a really nice feature for existing projects which want to adopt Groot. what prevents this from being implemented? Is there another workaround? @gonzalezreal
There is nothing that prevents this for being implemented. IMHO is a little bit out of scope, but perfectly possible to do it. To be honest, I don't have much time these days, so any PR is welcome, as long as the new functionality is backwards compatible, explicitly opt-in and covered by unit tests.
I do not have an explicit
id
field in any of my core data entities, but I would like to have a unique identifier for serialization -- in my application I use the NSManagedObject objectID property as the unique identifier, is it possible to have Groot serialize it along with the rest of my fields?The text was updated successfully, but these errors were encountered: