Skip to content

Commit

Permalink
Create some Markdown files for testing
Browse files Browse the repository at this point in the history
  • Loading branch information
maliayas committed Oct 26, 2013
1 parent baae56b commit ce38d78
Show file tree
Hide file tree
Showing 2 changed files with 100 additions and 0 deletions.
99 changes: 99 additions & 0 deletions tests/GFM.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,99 @@
# Strikethrough

Below text should be parsed as _strikethroughed_.

~~ Mistaken text. ~~

# Fenced Code Blocks

## In / Near List Items

Below fenced code blocks _should_ be highlighted.

---

* List item

```js
for (var i = 0; i < 10; i++) {
console.log(i);
}
```

* List item

```js
for (var i = 0; i < 10; i++) {
console.log(i);
}
```

---

Below are _not_ valid fenced code blocks according to the [GFM docs][GFM]. It says there must be a blank line before the code block. However, GitHub highlights them. So, they _should_ be highlighted.

---

* List item
```js
for (var i = 0; i < 10; i++) {
console.log(i);
}
```

* List item
```js
for (var i = 0; i < 10; i++) {
console.log(i);
}
```

## In / Near Paragraphs

Below is _not_ a _fenced_ code block, just a normal code block.

---

Paragraph

```js
for (var i = 0; i < 10; i++) {
console.log(i);
}
```

---

Below 2 blocks are fenced code blocks. They _should_ be highlighted.

---

Paragraph

```js
for (var i = 0; i < 10; i++) {
console.log(i);
}
```

Paragraph
```js
for (var i = 0; i < 10; i++) {
console.log(i);
}
```

---

Below is not any type of code block. It _should not_ be highlighted.

---

Paragraph
```js
for (var i = 0; i < 10; i++) {
console.log(i);
}
```

[GFM]: https://help.github.com/articles/github-flavored-markdown
1 change: 1 addition & 0 deletions tests/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
These are some example files to test if the syntax highlighting works correctly. They include some edge cases, too.

0 comments on commit ce38d78

Please sign in to comment.