Doesn’t YAML have a (seldom used) feature of a start and end of document marker? The “YAML frontmatter” that a few markdown documents have, uses this.
Comment on Everything about TOML format - Orchard Dweller
NewPerspective@lemmy.world 9 months ago
TOML and YAML both have the problem that if you receive an incomplete document, there’s a decent chance you can’t tell. JSON doesn’t have that because of the closing curly.
suy@programming.dev 9 months ago
EmergMemeHologram@startrek.website 9 months ago
On the other hand, I hate that with JSON you can only surge one document per file.
Some programs allow you to omit the outside braces, others require it.
But I do hate toml, and I don’t much like yaml either (why are there like 8 whitespace permutations?!)
Azzk1kr@feddit.nl 9 months ago
What’s wrong with TOML? I personally think it’s great for configuration purposes.
NostraDavid@programming.dev 9 months ago
One thing you can run into is that nesting things is hard in TOML: stackoverflow.com/…/does-toml-support-nested-arra…
The syntax is simply not built for that, because
.ini
format.
RubberElectrons@lemmy.world 9 months ago
Good point, I’d been interested in using toml
AMDmi3@lemmy.world 9 months ago
That’s not a problem of a format and should be handled by transport or storage.
Turun@feddit.de 9 months ago
It very much is an aspect of the format. You may deem it unimportant, but it’s a feature that is missing from toml and yaml.
AMDmi3@lemmy.world 9 months ago
It’s not a responsibly of the format, so, at most, it’s a mere side effect. In any practical process which could result with truncated data, even if it handles data with such property, it should be wrapped in a container which includes length. At the very least, it would allow to trace the source of truncation, e.g. was the data originally truncated, or was it truncated in the process. And the generating side should always provide success flag which should be properly handled, since it may produce syntactically correct, but semantically invalid data. Such as checking exit code of process which generates json/yaml in question
NewPerspective@lemmy.world 9 months ago
What about processes that terminate before writing the whole thing? You can’t protect against everything. Blame other processes all you want but the language spec allows for confusion.
AMDmi3@lemmy.world 9 months ago
You just check the exit code, no?