What a build contains
What a build of an application with spring_boot_starter_flutter_scene 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.
By key
build: AutoConfigurationBuild(key): true puts the module in every build, false leaves it out with all its code, and when the key is not set the Not set column decides.
| Module | Key | Not set | What it holds |
|---|---|---|---|
springBootStarterFlutterSceneAutoConfiguration |
spring.flutter.scene.enabled |
every build | The engine's start (sceneEngine) and its log, whether scenes draw here (sceneAvailability), the models and materials, the scenes' part of the start (sceneStart), sceneStatus and, with spring.flutter.scene.app.enabled: true, the application's scene. With false in the application's own configuration the module is left out of the build; a false set only in a profile switches its beans off in a running app that has them. |
springBootStarterFlutterSceneDebugAutoConfiguration |
spring.flutter.scene.debug.enabled |
debug and profile builds only | The scenes' tab of the debug panel (sceneDebugSection) and what it measures by (sceneDebug). The tab shows where the debug panel is in the build (spring.flutter.debug.enabled). |
A module left to notInRelease is dropped from Flutter's release builds and from dart compile exe. dart run and dart compile js / wasm define no dart.vm.product, so there the module stays when the key is not set; only false leaves it out.
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. |