Cool :)
Justification enough for me.
Jacques Nadeau wrote:
Just to clarify, my responses were in regards to HOCON.
On Mon, Jun 6, 2016 at 1:53 PM, Jacques Nadeau<[email protected]> wrote:
We use it a lot in Drill for configuration files. It serves this purpose
well. (We especially leverage the caoncatenation/overlay capbilities.)
I haven't thought enough about its use in this case to have an opinion one
way or the other.
On Mon, Jun 6, 2016 at 1:33 PM, Josh Elser<[email protected]> wrote:
At a glance, it looks like it would be a nice improvement over JSON with
the ability to still just provide json. Haven't had any practical
experience with it though (e.g. does it work as advertised).
Looks like they recommend ".conf" as the suffix
<snip>The JSON superset is called "Human-Optimized Config Object
Notation" or HOCON, and files use the suffix .conf.</snip>
Julian Hyde wrote:
HOCON is a superset of JSON that makes it easier for humans to edit JSON
files. For example, it supports multi-line strings, file inclusion,
comments.
Should Calcite support HOCON in addition to strict JSON for model files
any other config files? What should be the suffix of such files?
https://github.com/typesafehub/config<
https://github.com/typesafehub/config>
Julian
