Stephen Celis
Stephen Celis
@supermarin We could add `- (NSPredicate *)wherePredicateFor:(id)condition`, or something more suitably named. It doesn't seem as clean of an API, though, and it would likely be dropped for the next...
@supermarin Yeah, that would be ideal, but without the query builder on the 2.0 branch, there would be a lot of class-level API bloat.
This is implemented on the 2-0-experimental branch: https://github.com/supermarin/ObjectiveRecord/blob/2-0-experimental/Classes/CoreDataRelation.m#L112
> Format should be changeable per entity, so Person +dateFormat and Message +dateFormat could be different. Hm, should it be by entity? I think a global setting actually works well...
@supermarin In those cases, I think a transformation could solve the problem. An exception instead of a rule.
@supermarin Hm, so maybe the date formatter should go directly on the CoreDataManager class?
Adding this to the 2.0 milestone for consideration. We don't rely on ObjectiveSugar too many places, so maybe it's worth considering getting rid of the dependency.
Relates to #68.
/cc @supermarin
I like the idea. (CoreData errors are pretty unfriendly to begin with.) We should discuss it for the 2.0 roadmap. /cc @supermarin