From d940705c4ce02d12fac3c721d4f229c33a9520f8 Mon Sep 17 00:00:00 2001 From: TrapinchO <67415128+TrapinchO@users.noreply.github.com> Date: Wed, 3 Apr 2024 22:42:04 +0200 Subject: [PATCH] Update README.md --- README.md | 20 +++++++++----------- 1 file changed, 9 insertions(+), 11 deletions(-) diff --git a/README.md b/README.md index ec74050..e0edef2 100644 --- a/README.md +++ b/README.md @@ -13,20 +13,18 @@ can print out like this (or in any format you like!): Hi! miette also includes a screen-reader-oriented diagnostic printer that's enabled in various situations, such as when you use NO_COLOR or CLICOLOR settings, or on CI. This behavior is also fully configurable and customizable. For example, this is what this particular diagnostic will look like when the narrated printer is enabled: \ -diagnostic error code: oops::my::bad (link) -Error: oops! +Error: Received some bad JSON from the source. Unable to parse. + Caused by: missing field `foo` at line 1 column 1700 \ -Begin snippet for bad_file.rs starting -at line 2, column 3 +Begin snippet for https://api.nuget.org/v3/registration5-gz-semver2/json.net/index.json starting +at line 1, column 1659 \ -snippet line 1: source +snippet line 1: gs":["json"],"title":"","version":"1.0.0"},"packageContent":"https://api.nuget.o + highlight starting at line 1, column 1699: last parsing location \ -snippet line 2: text - highlight starting at line 1, column 3: This bit here -\ -snippet line 3: here -\ -diagnostic help: try doing it better next time? +diagnostic help: This is a bug. It might be in ruget, or it might be in the +source you're using, but it's definitely a bug and should be reported. +diagnostic error code: ruget::api::bad_json > **NOTE: You must enable the `"fancy"` crate feature to get fancy report