Solved Configurations - null vs nonexistant

How can I tell the difference between these two configurations?

Code:yaml

optionA: true
optionB: null
optionC: 7

Code:yaml

optionA: true
optionC: 7

How can I reproduce the first one?

 

_LB I guess you can set optionB to null, but that wouldn't change much. If it doesn't find the value at the specified path, it'll return null, unless you specify as a second argument the 'default' value, in case it doesn't find it in the config.

The only difference I can see between the two is that config.contains("optionB") will probably return true on the first, but false on the second.

 

_LB You could reproduce the first one by setting optionB to the String "null".
Then when reading it will also return a String..
I don't think there is any way to store an actual null object as thats just.. null.

 

OK, so it's just a quirk/limitation in the way the Configurations API works. Thanks!