avaje-config
avaje-config copied to clipboard
avaje
Application configuration / properties loading for JVM applications
`InitialLoader` / `InitialLoaderContext` does several things different than what the `Configuration.builder` does that are very hard to replicate with the builder. For example let us say I want to replicate...
- Adds a URI loader SPI for loading config from custom URIs - delete the `Parser` Class (it was basically just a map) this is what I got so far,...
So I still have not fully replaced our home grown config with `avaje-config` because of one feature that I can't decide whether to just work around or have it implemented...
We should probably handle this case: ```properties #a.properties load.properties=b.properties ``` ```properties #b.properties load.properties=a.properties ```
An experiment, created a simple parser with `jsonb` dependency as a separate module. Did this because I saw #94 was closed, and this seemed like the first simple thing that...
now can use the `${}` expression interpolation with `load.properties`
configures build to be [reproducible](https://maven.apache.org/guides/mini/guide-reproducible-builds.html)
### Loaders / `ConfigLoader2` 1. Each loader has a unique "prefix" 2. There are builtin core loaders such as `classpath file cmd stdin` 3. There are additional loaders like `aws`...
