How to use Dependency Injection in SwiftUI | Advanced Learning #16

Brilliant, I had to watch it multiple times but now it make more sense.
Thank you Nick

Nice.

Thanks Nick, good resume!

Excellence tutorials, you are the best teacher.

Thanks for sharing this. I'm a big fan on Uncle Bob and Clean Architecture. It appears to be working well with one view but how would you make it work with several views sharing the same data service?

For example, adding a record in one view and getting it in another view.

Using `PassthroughSubject` from Combine and adding a data publisher looks like huge added complexity IMO.

You are truly amazing!!!! Now I understand your crypto app code!!!

@Swiftful Thinking, how about passing VM's through .environmentObject? Or can you show how to initialize VM's on the top and pass it to he n child view? eg with this Dependencies class?
We need a better explanation of that

Hi man, your videos have been very helpful to me.

In general good work. Though you forget to mention that dependency injection can be very difficult to keep track of in big projects. Keeping track of all the dependencies is like visually having to keep track of a big DAG in your head. Do you know good DI container frameworks?

I’m absolutely confused as to why you would do this over @EnvironmentObject

Man, this is an excellent course. Thank you!
Do you have other video related to SOLID principales?

I broke thru the 'DataService' barrier; ... how many times can you say 'DataService' before a programmer passes out? hahaha. I watched until the end but still no further ahead. So do I get the point? NO ; I'll watch it again, again an again

...stressed you guys out... too late!

I skipped this video, too deep! but I'll try it now... I'll let you know... anyone have a shovel?

So easy to understand explanation. But the main reason im using singeleton is to using it from any class (ie. Network Manager, Socket Manager, Coredata manager). So, how can i share dataService class to other class? Thank you

Very useful video, but it would be great to have another video explaing dependency injection works with Core Data and a navigation of sub-views

Shouldn't a singleton have a private init ? Otherwise you can create multiple instances

So even though you inject the dependency, the injected value/class instance is still effectively subject to threading issues.

Hi Nick! Thank you for your awesome tutorial! I'm wondering that what if I want to create more DataServices for other Models, say UserDataService for Users, CommentDataService for Comments, etc. There might be different parameters for the same func name `getData()` or `addData()` or something else in different DataServices. I've tried to add the same func name with no parameters in DataServiceProtocol but got errors, swift think they are different functions. So how should I arrange my DataServiceProtocol or should I still use protocol? I'm still a beginner and I would really appreciate it if you could offer some suggestions.(Maybe I should move this comment to the protocol tutorial...😂)

What a minute how to inject a view model to a view, that's why I started watching the whole video. Good stuff BTW.

It's great video!!! amazing~~~
thank you for sharing this topic!!

Great video again! One question and this may take another boot camp to answer, lol. I see core data as a data service. It is common practice to use @Environment to hold the context of the core data entity. It is then easy to swap contexts for previews, testing… Could we and should we put our DataService master class, the one that holds many data services, into the Environment and use it in the same way? Like core data we would inject into the View init fetching criteria.

What we would do if we have a mock class that conforms to a DataService protocol, but the mock class doesn't need all of these methods of the protocol? For example it needs only 2 of 5

So awesome 👏🏾🌹

MVVM architecture is realy feast to eyes. After UIKit

Wonderful tutorial about dependency injection. Thanks you for your efforts and clear demonstrations. :)

Thank you very much, the entire last week I tried to learn how to replace my singleton Storageprovider (for Core Data) in an appropriate way with dependency injection for easier testing .... I struggled especially regarding initialization of the ViewModel (as StateObject)... everything I needed to know was in this video! 👍

Amazing! You never fail to teach a hard concept and make it easy. Thank you so much, you make a huge impact with your work :)

How would you use dependency injection if you also had another service communicating with the service that communicates directly with the viewModel? Example:

UserViewModel -> UserService -> StorageService/UserRepsoitory

Superb explanations.

Should the view not be passed the view model as dependency

He skipped the most important part which is where and how to create the dependencies...

Hi Nick, great content! -- it would be great to see an app from you with Clean Architecture from Uncle Bob using SwiftUI - it would be great to see the ways we can create dependency injection containers to manage them in our apps. Looking forwards to your new content

You're simply the best!

Blown Away ! Your tutorials are so rich with information. I have adapted my own logic based on your practices. Very succinct ! TY !

Great video man.

👍🏼👍🏼👍🏼

Hi sir. How do I transfer data between pages with Dependency Injection? Can you make an app with 2 or 3 pages about it?

I found your way of explaining things the best of all. Do you have any plans to make similar videos on Combine Framework?

I am following your videos, xcode 13 making too much problem. what is the solution?

I found this channel as the best for iOS developers

Could you do video lessons about the Combine?

Really great video!

Unrelated to the topic but I'm also learning great explanation skills and methods by watching your videos. I'm gonna steal it for my interviews lol.

So awesome! I really appreciate the way you explain things. Been looking for a while for videos that go in depth and really explain things instead of just showing one example. Keep up the good work!

Great post! About two thirds through the video I am on the edge of my seat thinking what about testing? Please don't wait to talk about that. You came through in the clutch. I realize you are going to expand on that in the future. Don't change a thing.

nice DI video, thankss 😁