From 64ca2d6c3a5b1138118d49bb2eb25e10b9a771b5 Mon Sep 17 00:00:00 2001 From: Koutheir Attouchi Date: Thu, 16 Jan 2025 13:07:47 -0500 Subject: [PATCH] Fix --- src/machine-readable-output.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/machine-readable-output.md b/src/machine-readable-output.md index 505db61..f1f68ac 100644 --- a/src/machine-readable-output.md +++ b/src/machine-readable-output.md @@ -13,7 +13,7 @@ Applications *may* (and in the case of forced loose coupling, *should*) make the * Programs *may* also provide their output as XML, [CBOR](https://cbor.io/), [MessagePack](https://msgpack.org/index.html), or other **self-describing** formats. * A self-describing format is one where the keys, or some equivalent, are part of the serialized output. * Formats like [protobuf](https://developers.google.com/protocol-buffers) are suitable as well, if up-to-date IDLs (e.g. `.proto` files) are published along with releases. One neat trick is to embed them into your binary and add a command to write them out to a given directory. -* If many lines of structured data are incrementally printed out, prefer a format like [newline-delimited JSON](http://ndjson.org/). This is the format used by Cargo's `--message-format json` option. +* If many lines of structured data are incrementally printed out, prefer a format like [newline-delimited JSON](https://jsonlines.org/). This is the format used by Cargo's `--message-format json` option. **Programs *must not* provide their output as [bincode](https://github.com/bincode-org/bincode) or other non-self-describing formats.** These formats are unsuitable for interoperability, where stability is paramount.