Skip to content

handle route globallyΒ #93

@AlexanderBollbach

Description

@AlexanderBollbach

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions