NDJSONRequest will parse the entire json request, for CoreData this is an issue because what you actually want put into your store is often a subtree. If we could switch between parsing to custom object to parsing to CoreData model that would provide a way to fix the issue. We can already switch from event driven parsing to another parsing method and back agains, so we just need to find a way to let the parser know the type of parsing has changes for a key. Maybe a CodeData models for keys method like the class for keys and property names for keys.
NDJSONRequest will parse the entire json request, for CoreData this is an issue because what you actually want put into your store is often a subtree. If we could switch between parsing to custom object to parsing to CoreData model that would provide a way to fix the issue. We can already switch from event driven parsing to another parsing method and back agains, so we just need to find a way to let the parser know the type of parsing has changes for a key. Maybe a CodeData models for keys method like the class for keys and property names for keys.