Good point, thanks!

Reminds of how Properties is poorly designed, it's extending Map but assuming no one will use the public methods it inherits.

Agreed we could look to refactor ConfigurationParseHelper to improve on this; to keep in mind that if we switch all methods to just use get(key) we need to also check in the defaults.. but this isn't exposed.

We should probably check for both "by the book" usage of Properties and for those using it in a more pragmatic way. I'm not sure we can, however, lookup a primitive true if people expect that to be inherited from a chained Properties instance.

My vote is to avoid Properties in future APIs evolutions, but yes let's explore some improvements already.

Thanks!