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

Re:I accidentally used YAML.parse instead of JSON.parse and ... by remram on Sunday January 23, 2022 @09:46PM (#30053121)

Edited with string escapes, the tab didn't make it through HN.

The error from PyYaml 5.3.1:

    yaml.scanner.ScannerError: while scanning for the next token
    found character '\t' that cannot start any token
      in "<unicode string>", line 4, column 1

[ Parent | on HN ]

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 ]

Re:I accidentally used YAML.parse instead of JSON.parse and ... by ak217 on Monday January 24, 2022 @12:34PM (#30060935)

Thanks, I'm finally able to reproduce this.

It would be great if instead of the histrionic message on CPAN (which amusingly accuses others of "mass hysteria"), the author would just say "YAML documents can't start with a tab while JSON documents can, making JSON not a strict subset of YAML".

The YAML spec should be updated to reflect this, but I wonder if a simple practical workaround in YAML parsers (like replacing each tab at the beginning of the document with two spaces before feeding it to the tokenizer) would be sufficient in the short term.

[ Parent | on HN ]

Re:I accidentally used YAML.parse instead of JSON.parse and ... by ingy on Monday January 24, 2022 @02:42PM (#30062858)

> "YAML documents can't start with a tab while JSON documents can, making JSON not a strict subset of YAML"

But YAML can start with tabs. Tabs are allowed as separating whitespace in most of the spec productions but are not allowed as indentation. Even though those tabs look like indentation, the spec productions don't interpret them as such.

See my comment above and esp see https://play.yaml.io/main/parser?input=CXsKCQkibGlzdCI6IFsKC...

Note: the YAML spec maintainers (I am one) have identified many issues with YAML which we are actively working on, but (somewhat surprisingly) we have yet to find a case where valid JSON is invalid YAML 1.2.

[ Parent | on HN ]

Re:I accidentally used YAML.parse instead of JSON.parse and ... by ak217 on Monday January 24, 2022 @04:11PM (#30064106)

Thanks for the clarification. Let's fix it in PyYAML then :)

Speaking of PyYAML, I recently ran into an issue where I had to heavily patch PyYAML to prevent its parse result from being susceptible to entity expansion attacks. It would be nice to at least have a PyYAML mode to completely ignore anchors and aliases (as well as tags) using simple keyword arguments. Protection against entity expansion abuse would be nice too.

[ Parent | on HN ]