Logging messages ([info] type) should be configurable to not print them at all

[Bender250]

For testing, it is difficult to find relevant information, when you are overwhelmed by the [info] messages.

[Bender250]

In contrast, for debug, we need much more information about the program's trace to be printed out. When config parsing fails, you always need to run debugger to find the issue. It would be nicer to see, which position of the config was parsed right now.

Possible workaround can be writing the debug info in json library. Change the methods json.at() and json.value() so they do not print only what is missing, but where is it missing (There is no key "source" in ).