You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The closest I could find is in the Spring Boot Relaxed Binding 2.0 document, which only says:
We recommend that properties are stored [...] in lowercase kabab format.
I think something stronger and/or more detailed is called for.
☞ If it would help, I'd gladly put in a PR with the additional paragraph or two, if you'll point me to the appropriate documentation (source).
Example
In case anyone doubts this behavior, I'm attaching a trivial demonstration built from start.spring.io with Spring Boot 2.7 & Java 17, but I am pretty sure this behavior dates back to 2.0, at least.
value.camelCase=v.cC
value.uniform-format=v.u-f
second.cc-via-cc=${value.camelCase}
second.uf-via-uf=${value.uniform-format}
second.cc-via-uf=${value.camel-case}
second.uf-via-cc=${value.uniformFormat}
# The first three work as expected. The fourth, referencing a property defined# in uniform format by using camelCase name, is not resolved.
philwebb
changed the title
Spring Boot resolution of placeholder names does not fully support "relaxed binding 2.0" - documentation enhancement
Document that property placeholders should use the canonical property name form
Jun 14, 2022
Uh oh!
There was an error while loading. Please reload this page.
This is a request to improve the documentation by mentioning that "placeholders" (the property names) must always be spelt either:
(I haven't considered environment variables here.)
This may seem obvious, but I could not find it documented anywhere; not
The closest I could find is in the Spring Boot Relaxed Binding 2.0 document, which only says:
I think something stronger and/or more detailed is called for.
☞ If it would help, I'd gladly put in a PR with the additional paragraph or two, if you'll point me to the appropriate documentation (source).
Example
In case anyone doubts this behavior, I'm attaching a trivial demonstration built from start.spring.io with Spring Boot 2.7 & Java 17, but I am pretty sure this behavior dates back to 2.0, at least.
The properties in the demo:
resolving-placeholders-demo.zip
The text was updated successfully, but these errors were encountered: