refactor: Use Spring boot API to manage unresolved placeholders#44
Open
FBibonne wants to merge 2 commits into
Open
refactor: Use Spring boot API to manage unresolved placeholders#44FBibonne wants to merge 2 commits into
FBibonne wants to merge 2 commits into
Conversation
…unresolved placeholders in properties WIP - Remove custom class extension with acces to non-public spring boot classes
…unresolved placeholders in properties : OK - Remove custom class extension with acces to non-public spring boot classes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Unresolved placeholders in properties make properties values resolution fail by default. The lib must not fail to display the raw value of the property : it was done using Spring non-public classes with reflexion. Now it is done using Spring Boot API.