Why are we templating YAML?

Re:Why are we templating YAML? by jrockway on Thursday February 07, 2019 @07:52PM (#19110261)

I don't mind YAML. I dislike that something things become strings and sometimes they become other types:

   foo: bar   # {"foo":"bar"}
   foo: "bar" # {"foo":"bar"}
   foo: 42    # {"foo":42}
   foo: "42"  # {"foo":"42"}

Other than that, no major complaints. My editor understands YAML and shows the indentation level in the background (highlight-indentation-mode) and auto-formats files so they all have consistent indentation (prettier-mode). As a result, it is not much of a nightmare to edit, despite the fact that semantic whitespace COULD cause you a lot of problems.

[ Parent | on HN ]

Re:Why are we templating YAML? by aldanor on Monday February 11, 2019 @05:30AM (#19133384)

How about...

    foo: yes  # "foo": true
    bar: YEs  # "bar": "YEs"
    baz: YES  # "baz": true

[ Parent | on HN ]

Re:Why are we templating YAML? by jrockway on Monday February 11, 2019 @11:43AM (#19135751)

Yeah, that's a little crazy. It's the classic case of in-band signalling. It never works. I wish quotes around strings were mandatory, then having 83 ways to say "true" would be OK. But when strings randomly get upgraded to other primitive types... it's a little weird.

[ Parent | on HN ]