5c8170656b
Currently the json-formatted outputs have no way to unambiguously determine which kind of message is being output. A consumer can look for specific fields in the json object (eg "message"), but there's no guarantee that in future some other kind of output will have a field of the same name. This PR adds a `"type"` field to add json outputs which can be used to unambiguously determine which kind of output it is. The mapping is: diagnostic: regular compiler diagnostics artifact: artifact notifications future_incompat: Report of future incompatibility unused_extern: Unused crate warnings/errors This matches the "internally tagged" representation for serde enums. |
||
|---|---|---|
| .. | ||
| json-and-color.rs | ||
| json-and-color.stderr | ||
| json-and-error-format.rs | ||
| json-and-error-format.stderr | ||
| json-bom-plus-crlf-multifile-aux.rs | ||
| json-bom-plus-crlf-multifile.rs | ||
| json-bom-plus-crlf-multifile.stderr | ||
| json-bom-plus-crlf.rs | ||
| json-bom-plus-crlf.stderr | ||
| json-invalid.rs | ||
| json-invalid.stderr | ||
| json-multiple.polonius.stderr | ||
| json-multiple.rs | ||
| json-multiple.stderr | ||
| json-options.polonius.stderr | ||
| json-options.rs | ||
| json-options.stderr | ||
| json-short.rs | ||
| json-short.stderr | ||