"yes as a boolean": yes
"yes as a string": "yes"
"yes as a string with tag": !!str yes
The third line causes the error in the title of the issue. Is there currently no support for the recommended schemas? If there isn't, there should be at least some documentation on how to add this support locally.
I'll "me too" this by linking to the other parts of the specs.
YAML 1.2 specification
YAML 1.1 specification
YAML 1.0 specification
Some call it type casting, some call it explicit types, and the YAML folks call it Explicit Tags. Since 1.0, according to the above specs.
I've just looked into this and it looks like the parser we use uses an alternate schema instead of the fail safe schema by default. Should be a simple fix.
@JPinkney yes please :)
End up here due to:
date_last_commit: !!timestamp "2020-01-29 09:38:43+00:00",
is causing this error: unknown tag <tag:yaml.org,2002:timestamp>
I'd like to tell the extension, _it's fine, relax_
Having the same problem with str
example: !!str 2019-10-10
causes unknown tag <tag:yaml.org,2002:str>
Same issue for integer
POSTGRES_PORT: !!integer 5432
is causing this error: unknown tag <tag:yaml.org,2002:integer>
Just put the exact value from the error message (between the angle brackets) into the yaml.customTags VSCode setting and mark it as scalar. Example:
"yaml.customTags": [
"tag:yaml.org,2002:binary scalar",
"tag:yaml.org,2002:timestamp scalar"
]
Still would love to see official support for tags from the failsafe schema.
Any updates on this?
Most helpful comment
End up here due to:
is causing this error:
unknown tag <tag:yaml.org,2002:timestamp>I'd like to tell the extension, _it's fine, relax_