Skip to content

Conversation

nosan
Copy link
Contributor

@nosan nosan commented Apr 30, 2025

Introduce the spring.configurationproperties.ignore-unresolvable-placeholders property to control whether an exception should be thrown when a property placeholder ${...} cannot be resolved.

See #18816

@nosan nosan changed the title Add a property to ignore unresolvable placeholders for @ConfigurationProperties Add an property to fail fast for unresolvable placeholders in @ConfigurationProperties Apr 30, 2025
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Apr 30, 2025
@nosan nosan changed the title Add an property to fail fast for unresolvable placeholders in @ConfigurationProperties Add a property to fail fast for unresolvable placeholders in @ConfigurationProperties Apr 30, 2025
@nosan nosan force-pushed the 18816 branch 2 times, most recently from a0a6a42 to 9308764 Compare May 1, 2025 09:22
…rationProperties

Introduce the `spring.configurationproperties.ignore-unresolvable-placeholders`
property to control whether an exception should be thrown when a property
placeholder `${...}` cannot be resolved.

Signed-off-by: Dmytro Nosan <[email protected]>
@snicoll
Copy link
Member

snicoll commented Oct 6, 2025

Thanks for the PR but I don't think we should focus on this property alone. We might want to customize the property replacement altogether and do it consistently (i.e. for the whole app). I am going to continue brainstorming on the original issue and your insights are very much appreciated.

@snicoll snicoll closed this Oct 6, 2025
@snicoll snicoll added status: declined A suggestion or change that we don't feel we should currently apply and removed status: waiting-for-triage An issue we've not yet triaged labels Oct 6, 2025
@nosan
Copy link
Contributor Author

nosan commented Oct 6, 2025

Thanks, @snicoll

Indeed, this PR was focused solely on @ConfigurationProperties, as it addressed the original issue and I didn't want to include more than necessary. I agree that it's better to have a broader option to control the entire application rather than just a part of it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: declined A suggestion or change that we don't feel we should currently apply
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants