Our great sponsors
-
-
Many parsers either default to YAML pre-1.2 or do not even expose a YAML 1.2 option. PyYAML has no 1.2 option, for example. So unless Ansible is using something other than PyYAML...
Relevant (open) PR: https://github.com/yaml/pyyaml/pull/555
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
TOML sucks for list of tables simply because they intentionally crippled inline tables to only be able to occupy one line. For ideology reasons ("we don't need to add a pseudo-JSON").
https://github.com/toml-lang/toml/issues/516
[[main_app.general_settings.logging.handlers]]
-
You might get a kick out of Concise Encoding then (shameless plug). It focuses on security and consistency of behavior.
In particular:
* How to deal with unrepresentable values: https://github.com/kstenerud/concise-encoding/blob/master/ce...
* Mandatory limits and security considerations: https://github.com/kstenerud/concise-encoding/blob/master/ce...
* Consistent error classification and processing: https://github.com/kstenerud/concise-encoding/blob/master/ce...
-
The simplest solution here would be to use JSON5 (https://json5.org/)
But sadly, it's also all about the ecosystem. VSCode for example doesn't come with JSON5 support out of the box. GitHub and many other tools / renderers and supports it at least in syntax highlighting.
-
I quite like CUELang (https://cuelang.org/), although it not yet widely supported.
It has a good balance between expressivity and readability, it got enough logic to be useful, but not so much it begs for abuses, it can import/export to yaml and json and features an elegant type system which lets you define both the schema and the data itself.
I hope it gains traction.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
I'm one of the authors of the YAML specification. https://yaml.org/spec/1.2.2/
To date we honestly have not identified a case where where valid JSON is not valid YAML 1.2.
If anyone can point out a case where this is true, please file an issue here: https://github.com/yaml/yaml-spec/issues/