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.
Comment on Everything about TOML format - Orchard Dweller
AMDmi3@lemmy.world 1 year agoThat’s not a problem of a format and should be handled by transport or storage.
NewPerspective@lemmy.world 1 year ago
AMDmi3@lemmy.world 1 year ago
You just check the exit code, no?
Turun@feddit.de 1 year 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 1 year 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