You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Interesting concept. I've thought about it in other lifecycle mechanisms, but not view controllers.
This will be different because UIViewController lifecycle methods are subclassed, rather than delegated. It's an interesting problem though.
Can you set the stage with a use case for how you would interact with these methods? I'm assuming from outside the controller, correct? Is there a particular navigation architecture (i.e. VIPER) that would benefit from this?
You're very right, indeed.
Model View Presenter for instance or any other architecture that separates the view from who controls it like VIPER, or MVVM or whatever. The presenter would be able to control everything from outside it, although I know it might be coupled to a specific type but I was only curious about all this concept.
It would be reaaaaally nice to have life cycle methods:
viewDidLoad
will/did appear/disappear
etc.
Thanks for this nice kit!
The text was updated successfully, but these errors were encountered: