toStringJSON about config

[havocp]

My question would be, why have a convenience thingy like this only for one set of render options?

If config.root().render(ConfigRenderOptions.concise().setFormatted(true)) is too verbose then I'd rather have a solution that also makes config.root().render( /* any options here */) less verbose, ideally. The ideas to improve this in Java are pretty limited though perhaps.

Adding a shortcut for just one set of render options doesn't seem to address the full issue.

ok.

I guess the real feature I am missing is a "standard", "canonical" way to represent config
in most popular formats: json and xml as a minimum;

in the spirit of HOCON, it better be "formatted" or as human-readlbe as possible;

for example, "verbose" compromise threshold for json would be to drop non-json
things like comments, but still make it formatted;

current default config.toString is pretty much unusable for me;