YAML: probably not so great after all (2017)

Post by spacemanmatt » Thu, Jun 21, 2018, 2:36 AM UTC

dmitriid wrote: post #126

Edmond wrote: post #118

Earlier quoted context omitted.

thanks for the broken link pointer, it will be fixed. the "So Much More" button is a link to the docs:) Here's the ConfigNode doc: http://codesolvent.com/doc/config-node/ The platform doc: http://codesolvent.com/doc/webapps/ If you're interested, send me an email (in my profile).

> the "So Much More" button is a link to the docs:) Yeah... No. It looks like a link to yet more marketing-speak, and the page it links to answers zero answers as to why I would ever want it. Hiding the product README in some nested folder in the source code is also a brilliant idea. So, nope. I’m sticking to my YMLs and EDNs.

Post by nojvek » Thu, Jun 21, 2018, 2:48 AM UTC

pacala wrote: post #300

chx wrote: post #63

Earlier quoted context omitted.

Drupal 8 uses YAML* as its configuration language because JSON doesn't support comments. That simple. Thank you for YAML, it does deliver for us: it's human readable and it's easy to parse (see below). * I mean, it uses an ill defined subset of YAML. The definition is "whatever the Symfony YAML parser supports".

Try https://jsonnet.org/ . Supports comments, plus a handful of additional useful features.

Post by sho » Thu, Jun 21, 2018, 2:52 AM UTC

joobus wrote: post #177

sho wrote: post #111

Earlier quoted context omitted.

> objects can't have a trailing comma This has caused me so much misery in the past, especially since none of the tools will tell you which line the offending comma is on. Great, somewhere in my thousand-plus-line JSON file is a tiny syntax error but you won't tell me where. Ended up having to regex for them. Didn't do wonders for my trust in JS tooling.

From the command line: python -m json.tool This will tell you where your file is messed up. There is also https://github.com/zaach/jsonlint

Post by mypalmike » Thu, Jun 21, 2018, 3:16 AM UTC

mottosso wrote: post #179

dharmab wrote: post #165

Earlier quoted context omitted.

How do I do something like: { # comment with a note about the value of foo "foo": "bar", # comment with a note about the value of baz "baz": "qux" } Without driving myself and future readers insane with fooComments and bazComments? What if I need a multiline comment explaining a yak-shaving story for why a key is set to a certain value? What if the object in question is a set of keyword arguments, and adding new fiel…

Ok, I'll bite. { "#": "A foo variable", "foo": true, "#": "A bar variable", "bar": false } Alternatively. { "# A foo variable": "", "foo": true, "# A multiline..": "", "# .. bar variable": "", "bar": false } Presto!

  print (json.dumps(json.loads(js_data), indent=2))

  {
    "bar": false,
    "foo": true,
    "# A multiline..": "",
    "# .. bar variable": "",
    "# A foo variable": ""
  }

Post by balloob » Thu, Jun 21, 2018, 3:24 AM UTC

Mister_Snuggles wrote: post #163

I've been playing with Home Assistant[0] recently and, as a result, getting exposed to YAML. I don't find it pleasant to work with at all. I'm sure a big part of that is how Home Assistant uses YAML for automation stuff[1] that would probably be better served by a real programming language. I think a big part of the unpleasantness comes from how non-obvious some things are. For example, why does the first automation…