Implicit Typing in StrictYAML about strictyaml HOT 12 CLOSED

I think we're going around in circles now.

from strictyaml.

This also happens in maps:

key: key2: value

ruamel.yaml.scanner.ScannerError: mapping values are not allowed here

vs.

key: key2 value

which is a string.

from strictyaml.

I'm not exactly sure what it is you are proposing here. Could you clarify?

from strictyaml.

In the FAQ it says that StrictYAML removes implicit typing, but this is still a thing as shown above.
I've seen YAML files like:

ssh-authorized-keys:
  - sha-rsa AAAB3Nz...
  - sha-rsa AAAB3Nz...

In this case you are kinda lucky because the syntax of the authorized_keys file doesn't contain a colon. Every element in ssh-authorized-keys is a string.
But if it would contain a colon like sha-rsa: AAAB3Nz... those elements will turn into maps but you would assume that the elements are still strings.

from strictyaml.

Not if you use validators.

from strictyaml.

key: key: value

print(load(yaml_string, Map({"key": Str()})).data)

ruamel.yaml.scanner.ScannerError: mapping values are not allowed here
  in "<unicode string>", line 1, column 9:
    key: key: value
            ^ (line: 1)

from strictyaml.

Yes, that isnt valid YAML. If you want to represent that you can do so by escaping though:

key: |
  key: value

key: 'key: value'

>>> print(load(yaml_string, Map({"key": Str()})).data)
{"key": "key: value"}

from strictyaml.

I know.
Take this for example:

url1: www.google.com
url2: http: //www.google.com

Tell a non-programmer that url2 doesn't work.
It could be even more hidden:
key: superlongrandomstringwhoopsarandomcolonappears: whoops

from strictyaml.

So... ?

from strictyaml.

So now you have:

• Implicit Typing: key: key: value vs key: key:value
• Explicit Typing: key: 'key: value' and the pipe syntax + noise
• Neither non-programmer friendly nor programmer friendly

from strictyaml.

Tell a non-programmer that url2 doesn't work.

That's what the error message with line numbers and a code snippet is for - to tell you that the code is invalid.

It could be even more hidden:

key: superlongrandomstringwhoopsarandomcolonappears: whoops

Hidden?

ScannerError: mapping values are not allowed here
  in "<unicode string>", line 1, column 52:
     ... mstringwhoopsarandomcolonappears: whoops
                                         ^ (line: 1)

from strictyaml.

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?

from strictyaml.