NSManagedObjectContext category

Question

Closed this issue 11 years ago · 4 comments

What do you think about this category? https://gist.github.com/buh/6643457

Answer 1 · 2013-09-21T13:45:06.000Z

Using [NSManagedObjectContext context] instead of [NSManagedObjectContext mainContext] requires you to know that you're currently in the main thread. It means moving information from being explicit to being implicit, which decreases readability. While boilerplate Core Data code is too verbose (hence, this lib), I do not believe writing less is always better. Readability is more important.
Often, you want to call [NSManagedObjectContext mainContext] and [NSManagedObjectContext backgroundContext] from different threads (in fact, I often call both mainContext and backgroundContext from the same method). The point of the performBlock method is that you can use managed contexts, which are thread safe, to manipulate managed objects, which are not thread safe, from wherever you are working.
Contexts do not belong to threads – this is the old confinement pattern. Coupling a context to a thread is misleading (even though it works).

Answer 2 · 2013-09-21T17:40:56.000Z

Thank you, Jesper, for your detailed comment! And I agree with you that readablity more important then shortness.

Answer 3 · 2013-09-21T20:30:40.000Z

Not a problem, Alexey. Hope I could be of some help.

Answer 4 · 2013-09-21T20:36:57.000Z

Yes, of course, thanks again. I decided to remove a category in the project and explain team that it would be better.