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
My understanding of NavigationState.route is that each of its RouteElementIdentifier elements corresponds to a Routable that is triggered. So if my route state goes from ["home"] to ["home", "favorites"] than the root Routable will push FavoritesVC (for example). So each successive RouteElementIdentifier that is appended during a SetRouteAction([] hands control off to a new Routable.
But what if I want to push a loading screen as the 3rd Routable. A loading screen could be presented from any VC. Is there a way to define the routing to a loading screen (say by presenting LoadingVC modally) once and have FavoritesVC inherit the ability? Because a ProfileVC along with 10 other VC's would reasonably present a loading screen.
The text was updated successfully, but these errors were encountered:
I currently have this implemented, but my global view is a Menu. I approached this by making a protocol, MenuDelegate that requires the implementation of my showMenu() function. This function triggers access to the MenuVC just like any other view, and it can dismiss itself as well.
Would an approach like that work for your use case? This is a problem I'm trying to improve upon myself.
@trentguillory@mjarvis
i thought of another way to do this. but it would involve changing the library. looking at the source, (specifically Router<T>.routingActionsForTransitionFrom), if my routing state goes from ["foo"] to ["foo", "bar"], than the Routable pushed for "foo" is charged with routing to "bar". Is it possible to extend ReSwiftRouter such that the "bar" route could be handled only by the Routable for "foo"?
My understanding of
NavigationState.route
is that each of itsRouteElementIdentifier
elements corresponds to aRoutable
that is triggered. So if my route state goes from["home"]
to["home", "favorites"]
than the rootRoutable
will pushFavoritesVC
(for example). So each successiveRouteElementIdentifier
that is appended during aSetRouteAction([]
hands control off to a newRoutable
.But what if I want to push a loading screen as the 3rd
Routable
. A loading screen could be presented from any VC. Is there a way to define the routing to a loading screen (say by presenting LoadingVC modally) once and haveFavoritesVC
inherit the ability? Because aProfileVC
along with 10 other VC's would reasonably present a loading screen.The text was updated successfully, but these errors were encountered: