aboutsummaryrefslogtreecommitdiffstats
path: root/tests/misc_default_line_ending.rs
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--tests/misc_default_line_ending.rs8
1 files changed, 5 insertions, 3 deletions
diff --git a/tests/misc_default_line_ending.rs b/tests/misc_default_line_ending.rs
index 531165c..b122c50 100644
--- a/tests/misc_default_line_ending.rs
+++ b/tests/misc_default_line_ending.rs
@@ -3,7 +3,7 @@ use micromark::{micromark, micromark_with_options, LineEnding, Options};
use pretty_assertions::assert_eq;
#[test]
-fn default_line_ending() {
+fn default_line_ending() -> Result<(), String> {
assert_eq!(
micromark("> a"),
"<blockquote>\n<p>a</p>\n</blockquote>",
@@ -35,7 +35,7 @@ fn default_line_ending() {
default_line_ending: LineEnding::CarriageReturn,
..Options::default()
}
- ),
+ )?,
"<blockquote>\r<p>a</p>\r</blockquote>",
"should support the given line ending"
);
@@ -47,10 +47,12 @@ fn default_line_ending() {
default_line_ending: LineEnding::CarriageReturn,
..Options::default()
}
- ),
+ )?,
// To do: is this a bug in `micromark.js` that it uses `\r` for earlier line endings?
// "<blockquote>\r<p>a</p>\r</blockquote>\n",
"<blockquote>\n<p>a</p>\n</blockquote>\n",
"should support the given line ending, even if line endings exist"
);
+
+ Ok(())
}