I accidentally used YAML.parse instead of JSON.parse and it worked

Re:I accidentally used YAML.parse instead of JSON.parse and ... by BiteCode_dev on Monday January 24, 2022 @07:13AM (#30056688)

> Honestly, I think a good configuration library should be more than a spec, it should come with a library that handles parsing/validation

You just described CUELang.

The type system allows to define a schema as well as the data, in the same file, or in 2 separate ones. Then you can call either a cli tool (that works on linux, windows or mac) or use the Go lib (or bind to it).

For compat, cue can import and export to yaml, json and protobuf, as well as validate them.

[ Parent | on HN ]

Re:I accidentally used YAML.parse instead of JSON.parse and ... by stavros on Wednesday January 26, 2022 @04:32AM (#30083485)

Isn't Dhall basically the same (=have the same set of features)?

[ Parent | on HN ]

Re:I accidentally used YAML.parse instead of JSON.parse and ... by BiteCode_dev on Wednesday January 26, 2022 @10:04AM (#30086312)

In the same way python and js are basically the same.

[ Parent | on HN ]

Re:I accidentally used YAML.parse instead of JSON.parse and ... by stavros on Wednesday January 26, 2022 @12:02PM (#30088101)

Exactly. So if I'm going to learn/use one of them, there's no clear winner, really. Both also seem to also have about the same amount of adoption (zero?).

[ Parent | on HN ]

Re:I accidentally used YAML.parse instead of JSON.parse and ... by chillfox on Monday January 24, 2022 @09:32AM (#30058024)

Ok, you have convinced me to give it a serious look.

[ Parent | on HN ]