What a build contains

What a build of an application with spring_boot_starter_flutter_security 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
springBootStarterFlutterSecurityAutoConfiguration The SecretStore (the platform's secure storage, or in memory on the web), secretTemplate, the AuthorizationWindow (the system's login window, or the browser and a loopback redirect on Windows and Linux; none on the web), principalNotifier and, outside a browser, when an OAuth2 registration is set: the DPoPKey, authorizedClientService and the OAuth2 client's registrations and token client.
springSecurityCoreAutoConfiguration (spring_security_core) Brought by the starter's dependency on spring_security_core. methodSecurityValidator stays in every build on purpose, as a safety net of security.

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 The security part, the navigation part and the Flutter parts and builders (spring_boot_starter_flutter, navigation), and the web part. The starter has no part of its own.

Good to know

See also