Skip to content

Commit

Permalink
Adjust expected errors for a rustdoc test
Browse files Browse the repository at this point in the history
`pulldown-cmark` has slightly different behavior between 0.11.0 and
0.11.2, causing one of the `unportable-markdown` tests to no longer emit
an error. Per [1], remove the error annotation and bless the output.

[1]: #128722 (comment)
  • Loading branch information
tgross35 committed Aug 19, 2024
1 parent b1b1dd1 commit 1eb1e18
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 22 deletions.
1 change: 0 additions & 1 deletion tests/rustdoc-ui/unportable-markdown.rs
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,6 @@ pub struct GfmFootnotes;
/// <https://github.com/pulldown-cmark/pulldown-cmark/pull/773>
///
/// test [^foo][^bar]
//~^ ERROR unportable markdown
///
/// [^foo]: test
/// [^bar]: test2
Expand Down
26 changes: 5 additions & 21 deletions tests/rustdoc-ui/unportable-markdown.stderr
Original file line number Diff line number Diff line change
@@ -1,31 +1,15 @@
error: unportable markdown
--> $DIR/unportable-markdown.rs:21:10
--> $DIR/unportable-markdown.rs:48:5
|
LL | /// test [^foo][^bar]
| ^^^^^^
LL | /// >bar
| ^
|
= help: confusing footnote reference and link
= help: confusing block quote with no space after the `>` marker
note: the lint level is defined here
--> $DIR/unportable-markdown.rs:8:9
|
LL | #![deny(rustdoc::unportable_markdown)]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
help: if it should not be a footnote, escape it
|
LL | /// test \[^foo][^bar]
| +
help: if the footnote is intended, add a space
|
LL | /// test [^foo] [^bar]
| +

error: unportable markdown
--> $DIR/unportable-markdown.rs:49:5
|
LL | /// >bar
| ^
|
= help: confusing block quote with no space after the `>` marker
help: if the quote is intended, add a space
|
LL | /// > bar
Expand All @@ -35,5 +19,5 @@ help: if it should not be a quote, escape it
LL | /// \>bar
| +

error: aborting due to 2 previous errors
error: aborting due to 1 previous error

0 comments on commit 1eb1e18

Please sign in to comment.