Can you possibly explain the @escaping closures and callback and the reason for this instead of making the function return something? New to iOS development
Hi Cesar, using callback function to return a value is a common approach to achieve asynchronous function in programming. In this case, the function have to be asynchronous as the network API call is not returning the value immediately. @escaping closure is just the Swift way of implementing callback.
Thank you for this wonderful tutorial! One question: so the in the dataFetchable protocol, the function needs to have the exact same name with the one inside ApiCaller right ?
Brother for learning iOS development do we need Mac laptop or any other alternatives and if we want to buy apple laptop what OS needs to be purchased bro
It was great video but I have different question. What should we do when we require a data to multiple places? I was thinking dependency injection is related to this but it seems it doesnt so I am little confused.
Should 256gb be enough for balancing college work and xcode projects or should i invest in 512gb storage? I am going to be purchasing a macbook air soon and don’t know how much storage xcode takes up. Thanks
This was a very nice tutorial. I know it's slightly off topic but how would you handle dependencies of your separated out targets. Let's say you network module depends on alamofire but you do not want you main app to depend on alamofire.
I mean correct me if I'm wrong but once you import 3rd party dependencies to assist with backend network calls wouldn't it now become a global asset to the whole project? Anything having to do with the API would require you importing in alamofire for each file no?
I’ve only been doing iOS development a few weeks, glad to see I’m not alone with Xcode being really flaky. Visual Studio isn’t perfect, but it seems way more stable and consistent.
