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
{{ message }}
This repository has been archived by the owner on Dec 5, 2019. It is now read-only.
I have a single APIImage class which inherits from MTLObject. I would like this class to implement the MTLManagedObjectSerializing protocol but I've run into a bit of a snag. My problem is that I have three distinct Image Entities implemented in Core Data all of which could potentially be created from the APIImage class. It seems as though MTLMangedObjectAdapter requires any class which implements the MTLManagedObjectSerializer protocol to define a unique Core Data entity name to which it will be mapped. Any suggestions? Even if I were to implement a hierarchy on the Core Data side (aka a single ImageEntity with three subentities) I don't believe I would be able to map the APIImage objects to their corresponding Core Data Entity class. Is this correct?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a single APIImage class which inherits from MTLObject. I would like this class to implement the MTLManagedObjectSerializing protocol but I've run into a bit of a snag. My problem is that I have three distinct Image Entities implemented in Core Data all of which could potentially be created from the APIImage class. It seems as though MTLMangedObjectAdapter requires any class which implements the MTLManagedObjectSerializer protocol to define a unique Core Data entity name to which it will be mapped. Any suggestions? Even if I were to implement a hierarchy on the Core Data side (aka a single ImageEntity with three subentities) I don't believe I would be able to map the APIImage objects to their corresponding Core Data Entity class. Is this correct?
The text was updated successfully, but these errors were encountered: