berkus
/
miette
mirror of https://github.com/zkat/miette.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix `clippy::doc_lazy_continuation` lints

This commit is contained in:
Bruce Mitchener 2024-08-06 09:20:49 +07:00
parent bf5aa3742f
commit 9284776a08
2 changed files with 16 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
README.md
View File

@ -28,9 +28,9 @@ diagnostic error code: ruget::api::bad_json
" />
> **NOTE: You must enable the `"fancy"` crate feature to get fancy report
output like in the screenshots above.** You should only do this in your
toplevel crate, as the fancy feature pulls in a number of dependencies that
libraries and such might not want.
> output like in the screenshots above.** You should only do this in your
> toplevel crate, as the fancy feature pulls in a number of dependencies that
> libraries and such might not want.
### Table of Contents <!-- omit in toc -->
@ -288,9 +288,9 @@ There are also similar [bail!] and [ensure!] macros.
automatically.
> **NOTE:** You must enable the `"fancy"` crate feature to get fancy report
output like in the screenshots here.** You should only do this in your
toplevel crate, as the fancy feature pulls in a number of dependencies that
libraries and such might not want.
> output like in the screenshots here.** You should only do this in your
> toplevel crate, as the fancy feature pulls in a number of dependencies that
> libraries and such might not want.
```rust
use miette::{IntoDiagnostic, Result};
@ -645,8 +645,8 @@ customize!
If you...
- ...don't know all the possible errors upfront
- ...need to serialize/deserialize errors
then you may want to use [`miette!`], [`diagnostic!`] macros or
[`MietteDiagnostic`] directly to create diagnostic on the fly.
then you may want to use [`miette!`], [`diagnostic!`] macros or
[`MietteDiagnostic`] directly to create diagnostic on the fly.
```rust

16
src/lib.rs
View File

@ -28,9 +28,9 @@
//! " />
//!
//! > **NOTE: You must enable the `"fancy"` crate feature to get fancy report
//! output like in the screenshots above.** You should only do this in your
//! toplevel crate, as the fancy feature pulls in a number of dependencies that
//! libraries and such might not want.
//! > output like in the screenshots above.** You should only do this in your
//! > toplevel crate, as the fancy feature pulls in a number of dependencies that
//! > libraries and such might not want.
//!
//! ## Table of Contents <!-- omit in toc -->
//!
@ -288,9 +288,9 @@
//! automatically.
//!
//! > **NOTE:** You must enable the `"fancy"` crate feature to get fancy report
//! output like in the screenshots here.** You should only do this in your
//! toplevel crate, as the fancy feature pulls in a number of dependencies that
//! libraries and such might not want.
//! > output like in the screenshots here.** You should only do this in your
//! > toplevel crate, as the fancy feature pulls in a number of dependencies that
//! > libraries and such might not want.
//!
//! ```rust
//! use miette::{IntoDiagnostic, Result};
@ -645,8 +645,8 @@
//! If you...
//! - ...don't know all the possible errors upfront
//! - ...need to serialize/deserialize errors
//! then you may want to use [`miette!`], [`diagnostic!`] macros or
//! [`MietteDiagnostic`] directly to create diagnostic on the fly.
//! then you may want to use [`miette!`], [`diagnostic!`] macros or
//! [`MietteDiagnostic`] directly to create diagnostic on the fly.
//!
//! ```rust,ignore
//! # use miette::{miette, LabeledSpan, Report};