Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'pass/inject' CoreDataStack question #2

Open
newmanw opened this issue Oct 21, 2014 · 0 comments
Open

'pass/inject' CoreDataStack question #2

newmanw opened this issue Oct 21, 2014 · 0 comments

Comments

@newmanw
Copy link

newmanw commented Oct 21, 2014

Hey Aaron! I attended your presentation on Core Data Concurrency @ 360iDev, thanks btw!!! I am just starting to dig through your demo code to try and start implementing some of this in a project I am working on. The question that comes to mind right away is where do I store this CoreDataStack object for access across multiple views in my app.

The easy way of course is to put it in the AppDelegate. But grabbing from the AppDelegate all the time is not really good practice.

I could create it in my AppDelete and inject it into my view controllers as needed. Wondering why you example did not take this approach. This also gets messy if you up a storyboard and you have to change where/how its gets injected.

Is each view supposed to create its own CoreDataStack object? That doesn't feel right to me for some reason, although it may very well be ok as I have no idea ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant