You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
let snippet = Snippet {
title: Some("failed to parse file".to_owned()),
footer: vec![],
slices: vec![Slice {
source: r#"This is an example
content of the slice
which will be annotated
with the list of annotations below."#
.to_string(),
line_start: 26,
origin: Some("chris.beep".to_owned()),
fold: false,
annotations: vec![SourceAnnotation {
label: "hello world".to_owned(),
annotation_type: AnnotationType::Error,
range: (13, 20),
}],
}],
};
This results in the following output:
error: failed to parse file
--> chris.beep:26:13
|
26 | This is an example
| ^^^^^^^ hello world
27 | content of the slice
28 | which will be annotated
29 | with the list of annotations below.
I would expect the underlining should wrap around to include the c of content on the next line. If we change the range from (13, 20) to (13, 21), that result includes the co of content being underlined.
The text was updated successfully, but these errors were encountered:
GodTamIt
added a commit
to GodTamIt/annotate-snippets-rs
that referenced
this issue
Jan 12, 2020
Fixes the error described in rust-lang#16. Previously, when a single character of
an annotation overflows to a new line, the DisplayList would incorrectly
consider that character on the same line. This change fixes this and
adds a new fixture test for this case.
Given this code:
This results in the following output:
I would expect the underlining should wrap around to include the
c
ofcontent
on the next line. If we change the range from(13, 20)
to(13, 21)
, that result includes theco
ofcontent
being underlined.The text was updated successfully, but these errors were encountered: