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
Hi @pgawlowski ,
this looks like view presentation logic, not much to do with routing itself.
Showing or hiding certain things in the view should be done by the presenter or the view itself.
If this is a problem that you need to solve through the entire application, I suggest you to create some BaseView class with properties like "shouldShowNavigationBar", "shouldShowTabBar", etc. They could have a default "true" value and you could override them wherever you need them.
Then your "BaseView" could check these values in the viewWillAppear, viewWillDisappear and do as told.
@ferranabello
Any hints on advanced navigation?
Routing examples:
let's start LoggedOutModule without navigation bar
we've got 2 paths:
Register process got 3 steps:
After register process we should unwind/jump back/show LoggedOutModule once again (without navigationBar).
How to handle whole navigation bar embedding/showing/hiding process + backrouting to previous modules (without navigation bars e.x).
My current idea is for showing-hiding of navigation controller is
And for routback to view is to just dismiss view which is currently presented over LoggedOutView
Is this correct approach?
The text was updated successfully, but these errors were encountered: