miette
miette copied to clipboard
zkat
Fancy extension for std::error::Error with pretty, detailed diagnostic printing.
`miette` supports adding multiple labels to an error, but there seems to be a baked-in assumption that all labels refer to the same source file. This is proving to be...
This might be a false positive (as indicated by miri in its help text), but I figured it's better to report it and have it be a false report than...
Only string literals are accepted, which is not friendly to gettext.
I'm currently making snapshot tests with non-ansi theme: ``` miette::GraphicalReportHandler::new_themed(miette::GraphicalTheme::unicode_nocolor()) ``` but it produces ansi characters for the links: ``` ]8;;https://eslint.org/docs/rules/no-cond-assign\(link)]8;;\ ``` It seems like the characters are hard code...
I would expect these two error types to be equivalent: ``` #[derive(Debug, Error, Diagnostic)] #[error("error!")] struct MyError { #[help] help_message: String, } #[derive(Debug, Error, Diagnostic)] #[error("error!")] #[help("{help_message}")] struct MyError {...
Hi. I wonder if it's possible to have a Label that span at end of source. My current workaround is to create a span that point to the last token...
`thiserror` has [a trait](https://github.com/dtolnay/thiserror/blob/master/src/display.rs) to allow writing code like this: ``` #[derive(Debug, Error)] #[error("failed to open {path}")] struct MyError { path: PathBuf, } ``` This doesn't work in miette format...
Label locations do not correctly account for the actual width of characters. The specific case I tested was for `☃` which is treated as being 3-wide because it is 3...
Previously `#[diagnostic_source]` did not correctly render the inner diagnostic. This PR fixes that. There's a change here that can be considered controversial: - Only print newlines when there is an...
(Sorry to not provide a proper repro. I’ll provide one later if you want, just wanted to get the issue opened before I forget). If I have code indented with...
