You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just had a funny realisation that when we load files and try Jsonnet first, if Jsonnet fails because of a runtime error (as opposed to, for example, a parser error) then we'll fallback to YAML.
Sadly, YAML will accept almost anything, including valid Jsonnet. So we end up awkwardly parsing Jsonnet as YAML which is unlikely to be what people want at all 😂
We should ensure that if the Jsonnet error is a runtime error we don't try parsing it as YAML.
Example is:
{
key:error'oh no',
}
Which YAML will parse happily as:
{
"key": "error 'oh no',"
}
The text was updated successfully, but these errors were encountered:
Just had a funny realisation that when we load files and try Jsonnet first, if Jsonnet fails because of a runtime error (as opposed to, for example, a parser error) then we'll fallback to YAML.
Sadly, YAML will accept almost anything, including valid Jsonnet. So we end up awkwardly parsing Jsonnet as YAML which is unlikely to be what people want at all 😂
We should ensure that if the Jsonnet error is a runtime error we don't try parsing it as YAML.
Example is:
Which YAML will parse happily as:
The text was updated successfully, but these errors were encountered: