spring/spring-boot
1
0
Fork 0
mirror of https://github.com/spring-projects/spring-boot.git synced 2026-10-08 10:19:13 +00:00
Code Issues Projects Releases Wiki Activity

Merge branch '3.5.x' into 4.0.x

Browse Source 
Closes gh-49851
This commit is contained in:
Stéphane Nicoll
2026-03-31 10:31:10 +02:00
parent 954fd3d8cb 6fe81dd196
commit 3c16fe6f4b
1 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/spring-boot-docs/src/docs/antora/modules/reference/pages/features/external-config.adoc
+12
View File
@@ -852,6 +852,18 @@ TIP: To use a reserved keyword in the name of a property, such as `my.service.im
[[features.external-config.typesafe-configuration-properties.default-values]]
=== Default Values
Default Values defined in configuration properties are not reflected in the javadoc:org.springframework.core.env.Environment[].
In the examples above, the `enabled` property of `MyProperties` bound to `my.service` is `false` by default.
However, `my.service.enabled` is not available in the `Environment` with a value of `false` if no such property is set by the user.
Concretely, this prevents you to use `@Value(${"my.service.enabled"})` or `my.service.enabled` as a placeholder in configuration properties without explicitly providing a default.
If you need to query the javadoc:org.springframework.core.env.Environment[] for that property, for instance in a javadoc:org.springframework.context.annotation.Condition[] implementation, the default needs to be provided as well.
[[features.external-config.typesafe-configuration-properties.enabling-annotated-types]]
=== Enabling @ConfigurationProperties-annotated Types