Open strokyl opened 9 months ago
Hi
If we look implementation of orElse
then we see that secondary ConfigSource
will be used if we get exception while parsing config from first ConfigSource
. And now ConfigSource
is renamed to ConfigProvider
.
I consider that it's correct behaviour.
For your case, we should create, for example, a merge
method.
If we look implementation of
orElse
then we see that secondary ConfigSource will be used if we get exception while parsing config from first ConfigSource
In test("does not work but should")
the first ConfigSource does not fail and return a valid result with is an empty list
Here is a test:
Here is the output:
I would expect that when the first datasource have an empty list for the given path and there is nothing on the second datasource, we get an empty list and not an error.