What a build contains
What a build of an application with spring_boot_starter_flutter_navigation contains, and when something is not in it. A module that follows a key reads it when build_runner runs, from application.yml or application.properties without a profile (see Modules left out of the build). The modules of the packages it depends on come with it: for spring_boot_dart, see Auto-configuration.
Always in
No build: and no platform:: in every build of an application that depends on the starter.
| Module | What it holds |
|---|---|
springBootStarterFlutterNavigationAutoConfiguration |
The route and branch scopes, the navigation (every ScreenRoutes bean put together and checked at the start, the RouteFilter beans, the redirects and first address), the RouteTemplate and the router SpringApp builds the app widget on. |
By key and by platform
Nothing is switched: no module of this starter follows a key or a platform, so all of it is in every build.
What the generator writes for it
A part of the generator (see Starter parts) runs only when the application reaches its package.
| Part or builder | What it does |
|---|---|
Navigation part (spring_boot_starter_flutter_navigation) |
Scans @ScreenRoute and @RouteShell widgets; writes the ScreenRoutes bean of a module, the constants of each screen (extension BookPageRoute on BookPage) and the routes and shells of spring_metadata.json. |
Builder spring_flutter_deep_links |
Blocks of Info.plist, Runner.entitlements and AndroidManifest.xml, and the domains' apple-app-site-association and assetlinks.json; only when spring.flutter.navigation.deep-links.* is set. |
| Through its dependencies | The Flutter parts and builders, and the web part, since the starter depends on spring_boot_starter_flutter (its page) and spring_web_dart. |