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

Re:I accidentally used YAML.parse instead of JSON.parse and ... by notreallyserio on Sunday January 23, 2022 @10:45PM (#30053491)

If it continues to be hard to share, I suggest encoding it as a base64 string so folks can decode it into a file with exactly the right contents.

[ Parent | on HN ]

Re:I accidentally used YAML.parse instead of JSON.parse and ... by CameronNemo on Sunday January 23, 2022 @10:58PM (#30053578)

This is, unwittingly, the most YAML-relevant comment in this thread.

[ Parent | on HN ]

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

Not base64, but this should be easy to reproduce:

  $ printf '{\n\t"list": [\n\t\t{},\n\t\t{}\n\t]\n}\n' > test.json

  $ jq < test.json 
  {
    "list": [
      {},
      {}
    ]
  }

  $ yamllint test.json 
  test.json
    2:1       error    syntax error: found character '\t' that cannot start any token (syntax)

[ Parent | on HN ]