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
I was hoping to avoid null entirely, but it looks like maybe we can't since lots of YAML in the wild contains null mappings. E.g. this example from the Score documentation
In it, resources.db.host, and resources.db.name are both null literals. These properties are equivalent to saying:
host: nullname: null
or
host: ~name: ~
As much as I would like to not have null in PlatformScript at all, if we want all YAML values to be valid platform script, as well as to deserialize and serialize back all wild programs, we will need to support it.
I would love for someone to prove me wrong.
The text was updated successfully, but these errors were encountered:
null
is a valid both as a YAML value, and also as a key in a YAML mapping, but we don not support it.https://yaml.org/type/null.html
I was hoping to avoid null entirely, but it looks like maybe we can't since lots of YAML in the wild contains null mappings. E.g. this example from the Score documentation
In it,
resources.db.host
, andresources.db.name
are bothnull
literals. These properties are equivalent to saying:or
As much as I would like to not have
null
in PlatformScript at all, if we want all YAML values to be valid platform script, as well as to deserialize and serialize back all wild programs, we will need to support it.I would love for someone to prove me wrong.
The text was updated successfully, but these errors were encountered: