Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Ability for ConfigSourceProvider to use Config
See original GitHub issueIt would be nice if it was possible for ConfigSourceProvider instances to read the current Config of higher ordinal sources for use in defining it.
For instance, a config property in system or microprofile-config.properties that specifies a list of directories that contain config elements, which a ConfigSourceProvider can reference to retrieve. At present there’s no way to do this, meaning values need to be hard coded into the instance directly as to where something might be.
Might require a “piecemeal” construction of Config so that each lower ordinal can take the Config up to that point and use it
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:37 (35 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Implemented a feature in SmallRye Config to support this: https://github.com/smallrye/smallrye-config/pull/313
I understand. So, you think that both should different solutions? Ideally if we could find something that works for both it would be great, but yes, in CDI it might be tricky.