Improve origin of imported config #23018
Assignees
Labels
theme: config-data
Issues related to the configuration theme
type: enhancement
A general enhancement
Milestone
Comments
wilkinsona
changed the title
philwebb
added a commit
that referenced
this issue
Aug 28, 2020
Update the `Origin` interface to include a default `getParent()` method which can be used to get the parent origin. The `TextResourceOrigin` has been updated to implement the method against the source `Resource`. A new `OriginTrackedResource` implementation allows any `Resource` to be decorated and carry an optional `Origin`. Ultimately this will allow us to include parent `Origin` information on properties loaded via a `PropertySourceLoader` without needing any changes to that interface. See gh-23018
philwebb
added a commit
that referenced
this issue
Aug 28, 2020
Allow `ConfigDataLocationResolvers` to access `Origin` information for locations so that they can be used as a parent origin of loaded items. The `ResourceConfigData...` classes have been reworked so that loaded `PropertySources` include the parent origin. See gh-23018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
The origin of a
spring.config.importlocation isn't very clear at the moment. It would be nice if we could show a full chain of where it came from.The text was updated successfully, but these errors were encountered: