routerWalkFile top-level constant

String const routerWalkFile

The path in an app of the locations that the walk of the test of the router role goes to, which the matrix writes: walkedLocations, the locations of the routes that need no values, each with the full name of its route (FacadeRoute.fullName), the location, created as const from its class of the navigation of the role, and the type of the screen that the route shows. They are in the order of the routes of the app (RouterFacade.routes).

The file also says what the router shows for each of them, with two functions that every app gets, so that the walk is the same in an app with guards of the routes (RouterFacade.guards) and in one without, which has nothing of what the role generates for them:

• shownFor(walked), the full name of the route and the type of the screen that the router shows when it is asked to show walked, a ShownScreen. In an app without guards, those are the ones of walked. In an app with guards, they are the ones of the target of the guard that keeps the user from walked, as redirectOf() of the role says; else startOfApp for a location in a flow that is over, as flowIsOver() of the role says; else the ones of walked. The targets are in guardTargets, in the order of the guards, those of the gates first and then those of the guards that stand for a condition, each once, also those that are not among the first routerWalkLimit locations. startOfApp is the screen that the app starts on: that of the route that the role chose (RouterRole.startIn), with the name of that route, or the fallback start screen of the app entry role (AppEntryRole.fallbackStartScreen) without the name of a route, in an app that no route can start;
• closedGuards(), the full names of the guards that do not allow, in the order of routeGuards of the role, a guard whose condition does not hold among them; none in an app without guards.

Implementation

const routerWalkFile = 'integration_test/router_walk/locations.dart';