Andrey Marinchuk
Andrey Marinchuk
You can ignore it or redefine the value (i.e., set to null and use hasPathOrNull(String) instead of hasPath(String) in code). Alternatively, rename the "value" to "value_src" in base.conf and append...
I'm ready to spent some time and prepare pool request, but need to know which way is preferred. The first is the only one will not break the compatibility. But...
@havocp, could you see this PR? It introduces the new include syntax which could be usefull in some cases and should not brake any current usage.
Hello, trying to use this great library, but we have to support property configs with settings like ``` xxx.yyy=true xxx.yyy.zzz="Something" ``` Is it possible to make properties parsing compatible to...
I've realized that putting property value as __value__ object key in the case of conflict was not a good idea. We have dynamic config file like: ``` base.object1 = class.name.First...
We managed to successfully migrate from properties file. We've adopted the following three rules: * `xxx = true/false; xxx.yyy = ...`: typically xxx.yyy doesn't make sence for xxx = false,...
> would it be simpler to wrap the `value` field in the constructor? though I suppose that uses memory more permanently so I don’t know. value is passing to the...
Great PR, with this change configuration beans can be finally made immutable!
There is ready PR for this feature: https://github.com/lightbend/config/pull/643
Well, one of the possible solution is to make the detailed area with the real unescaped value of selected note under the jsoneditor element (I think it could be implemented...