Implicit Typing in StrictYAML

Consider this YAML:

array:
  - string 1!
  - string: 2?

Which parses into this:

{'array': ['string 1!', {'string': '2?'}]}

The value determines its type. You’ve eliminated this behavior for primitive types:

python: 3.5.3
postgres: 9.3

Both are strings. But there is still implicit typing between string and map.

An array element syntax like:

array:
  -
  key1: value1
  key2: value2
  -
  key1: value1
  key2: value2
  - some: text

would fix this behavior but then it wouldn’t be a subset of YAML anymore 😄

[crdoconnor]

I think we’re going around in circles now.

[vnc5]

So we have a parser error determined by the content of a value: key: key: value vs key: key:value Implicit Typing determined by the content of a value in valid YAML:

array:
  - key: value
  - key:value

which will lead to errors in unvalidated programs. Validation error determined by the content of a value:

array:
  - key: value

load(yaml_string, Map({"array": Seq(Str())}))

strictyaml.exceptions.YAMLValidationError: when expecting a str
found mapping/sequence
  in "<unicode string>", line 2, column 1:
    - key: value
    ^ (line: 2)

What about the goals stated in the FAQ?