mirror of
https://github.com/discourse/discourse.git
synced 2024-12-11 21:36:07 +08:00
71d37953d5
We used many global functions to handle tests when they should be imported like other libraries in our application. This also gets us closer to the way Ember CLI prefers our tests to be laid out.
39 lines
854 B
JavaScript
39 lines
854 B
JavaScript
import PrettyText, { buildOptions } from "pretty-text/pretty-text";
|
|
|
|
module("lib:details-cooked-test");
|
|
|
|
const defaultOpts = buildOptions({
|
|
siteSettings: {
|
|
enable_emoji: true,
|
|
emoji_set: "emoji_one",
|
|
highlighted_languages: "json|ruby|javascript",
|
|
default_code_lang: "auto",
|
|
},
|
|
censoredWords: "shucks|whiz|whizzer",
|
|
getURL: (url) => url,
|
|
});
|
|
|
|
test("details", (assert) => {
|
|
const cooked = (input, expected, text) => {
|
|
assert.equal(
|
|
new PrettyText(defaultOpts).cook(input),
|
|
expected.replace(/\/>/g, ">"),
|
|
text
|
|
);
|
|
};
|
|
cooked(
|
|
`<details><summary>Info</summary>coucou</details>`,
|
|
`<details><summary>Info</summary>coucou</details>`,
|
|
"manual HTML for details"
|
|
);
|
|
|
|
cooked(
|
|
"[details=testing]\ntest\n[/details]",
|
|
`<details>
|
|
<summary>
|
|
testing</summary>
|
|
<p>test</p>
|
|
</details>`
|
|
);
|
|
});
|