4 ms·
Yes, without the quotes, the IPv6 address gets interpreted a YAML mapping/dict because of the colon(s). Perhaps the trap is the complacency that YAML induces b
by AceJohnny2 3y ago
Yes, without the quotes, the IPv6 address gets interpreted a YAML mapping/dict because of the colon(s).
Perhaps the trap is the complacency that YAML induces by not requiring quotes around keys/values, and so text risks being interpreted in unexpected ways. The infamous Norway Problem has the same root cause.
- esbeeb 3y ago...and TOML would have dodged this, because it requires the double-quotes in both cases (IPv4 and 6), like you say.
- xelxebar 3y ago> Yes, without the quotes, the IPv6 address gets interpreted a YAML mapping/dict because of the colon(s). This is incorrect. The colon needs to be followed by whitespace for it to indicate a key-value pair. You can check this with the reference parser (and a bunch of others!) online: https://play.yaml.io/main/parser?input=YWxsb3dlZC1pcHM6IFswLjAuMC4wLzAsIDIwMDE6ZmU6YWQ6ZGU6YWQ6YmU6ZWY6MS8yNF0K https://play.yaml.io/main/parser?input=YWxsb3dlZC1pcHM6IFswL...
- TeMPOraL 3y agoEven in the first position? That makes it no longer be the claimed "superset of JSON", since (AFAIK) {"key":"value"} (with no whitespace) is valid JSON.
- xelxebar 3y agoFor delimited collections, so within {} and [], if the key is quoted, then you don't need the whitespace. So your example parses as expected as does `{"key":value}`, but `{key:value}` turns into `{"key:value": null}`.
- AceJohnny2 3y agoThat looks very interesting, but can you provide a screenshot of the results, for someone who doesn't have Docker?