What a build contains
What a build of an application with spring_boot_starter_flutter_material 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 |
|---|---|
springBootStarterFlutterMaterialAutoConfiguration |
Material Design for the themes (MaterialThemeDesign), the themes as ThemeData (materialThemes), the MaterialApp of spring.flutter.app.type: material (materialAppFactory) and Material's page routes for the navigation starter (materialPageRoutes). |
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 |
|---|---|
| Through its dependencies | No part of its own. The parts and builders of spring_boot_starter_flutter run, since the starter depends on it. |