StarMirror/blackfriday
1
0
Fork 0
mirror of https://github.com/russross/blackfriday.git synced 2024-03-22 13:40:34 +08:00
Code Issues Projects Releases Wiki Activity
46c73eb196
blackfriday/block_test.go

1804 lines
49 KiB
Go
Raw Normal View History

fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
//
simplified BSD license
2011-06-28 10:11:32 +08:00
// Blackfriday Markdown Processor
// Available at http://github.com/russross/blackfriday
//
// Copyright © 2011 Russ Ross <russ@russross.com>.
version number, few more options for command-line tool
2011-06-29 01:30:10 +08:00
// Distributed under the Simplified BSD License.
simplified BSD license
2011-06-28 10:11:32 +08:00
// See README.md for details.
fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
//
//
// Unit tests for block parsing
//
package blackfriday
import (
Make test values more readable, add additional test cases.
2015-11-01 05:35:21 +08:00
"strings"
fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
"testing"
)
Allow configurable header ID prefix/suffixes. This is specifically driven by the Hugo usecase where multiple documents are often rendered into the same ultimate HTML page. When a header ID is written to the output HTML format (either through `HTML_TOC`, `EXTENSION_HEADER_IDS`, or `EXTENSION_AUTO_HEADER_IDS`), it is possible that multiple documents will hvae identical header IDs. To permit validation to pass, it is useful to have a per-document prefix or suffix (in our case, an MD5 of the content filename, and we will be using it as a suffix). That is, two documents (`A` and `B`) that have the same header ID (`# Reason {#reason}`), will end up having an actual header ID of the form `#reason-DOCID` (e.g., `#reason-A`, `#reason-B`) with these HTML parameters. This is built on top of #126 (more intelligent collision detection for `EXTENSION_AUTO_HEADER_IDS`).
2014-11-24 09:37:27 +08:00
func runMarkdownBlockWithRenderer(input string, extensions int, renderer Renderer) string {
return string(Markdown([]byte(input), renderer, extensions))
}
added simplified interface for common usage
2011-06-29 05:55:27 +08:00
func runMarkdownBlock(input string, extensions int) string {
htmlFlags := 0
htmlFlags |= HTML_USE_XHTML
fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
complete page rendering is now an option in the library
2011-06-30 00:08:56 +08:00
renderer := HtmlRenderer(htmlFlags, "", "")
fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
Allow configurable header ID prefix/suffixes. This is specifically driven by the Hugo usecase where multiple documents are often rendered into the same ultimate HTML page. When a header ID is written to the output HTML format (either through `HTML_TOC`, `EXTENSION_HEADER_IDS`, or `EXTENSION_AUTO_HEADER_IDS`), it is possible that multiple documents will hvae identical header IDs. To permit validation to pass, it is useful to have a per-document prefix or suffix (in our case, an MD5 of the content filename, and we will be using it as a suffix). That is, two documents (`A` and `B`) that have the same header ID (`# Reason {#reason}`), will end up having an actual header ID of the form `#reason-DOCID` (e.g., `#reason-A`, `#reason-B`) with these HTML parameters. This is built on top of #126 (more intelligent collision detection for `EXTENSION_AUTO_HEADER_IDS`).
2014-11-24 09:37:27 +08:00
return runMarkdownBlockWithRenderer(input, extensions, renderer)
}
func runnerWithRendererParameters(parameters HtmlRendererParameters) func(string, int) string {
return func(input string, extensions int) string {
htmlFlags := 0
htmlFlags |= HTML_USE_XHTML
renderer := HtmlRendererWithParameters(htmlFlags, "", "", parameters)
return runMarkdownBlockWithRenderer(input, extensions, renderer)
}
fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
}
added simplified interface for common usage
2011-06-29 05:55:27 +08:00
func doTestsBlock(t *testing.T, tests []string, extensions int) {
Allow configurable header ID prefix/suffixes. This is specifically driven by the Hugo usecase where multiple documents are often rendered into the same ultimate HTML page. When a header ID is written to the output HTML format (either through `HTML_TOC`, `EXTENSION_HEADER_IDS`, or `EXTENSION_AUTO_HEADER_IDS`), it is possible that multiple documents will hvae identical header IDs. To permit validation to pass, it is useful to have a per-document prefix or suffix (in our case, an MD5 of the content filename, and we will be using it as a suffix). That is, two documents (`A` and `B`) that have the same header ID (`# Reason {#reason}`), will end up having an actual header ID of the form `#reason-DOCID` (e.g., `#reason-A`, `#reason-B`) with these HTML parameters. This is built on top of #126 (more intelligent collision detection for `EXTENSION_AUTO_HEADER_IDS`).
2014-11-24 09:37:27 +08:00
doTestsBlockWithRunner(t, tests, extensions, runMarkdownBlock)
}
func doTestsBlockWithRunner(t *testing.T, tests []string, extensions int, runner func(string, int) string) {
bounds checking stress tests
2011-07-04 00:51:07 +08:00
// catch and report panics
var candidate string
defer func() {
if err := recover(); err != nil {
add error message when panic has been raised within `doTestsBlock()`
2014-03-31 03:59:20 +08:00
t.Errorf("\npanic while processing [%#v]: %s\n", candidate, err)
bounds checking stress tests
2011-07-04 00:51:07 +08:00
}
}()
fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
for i := 0; i+1 < len(tests); i += 2 {
input := tests[i]
bounds checking stress tests
2011-07-04 00:51:07 +08:00
candidate = input
fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
expected := tests[i+1]
Allow configurable header ID prefix/suffixes. This is specifically driven by the Hugo usecase where multiple documents are often rendered into the same ultimate HTML page. When a header ID is written to the output HTML format (either through `HTML_TOC`, `EXTENSION_HEADER_IDS`, or `EXTENSION_AUTO_HEADER_IDS`), it is possible that multiple documents will hvae identical header IDs. To permit validation to pass, it is useful to have a per-document prefix or suffix (in our case, an MD5 of the content filename, and we will be using it as a suffix). That is, two documents (`A` and `B`) that have the same header ID (`# Reason {#reason}`), will end up having an actual header ID of the form `#reason-DOCID` (e.g., `#reason-A`, `#reason-B`) with these HTML parameters. This is built on top of #126 (more intelligent collision detection for `EXTENSION_AUTO_HEADER_IDS`).
2014-11-24 09:37:27 +08:00
actual := runner(candidate, extensions)
fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
if actual != expected {
t.Errorf("\nInput [%#v]\nExpected[%#v]\nActual [%#v]",
bounds checking stress tests
2011-07-04 00:51:07 +08:00
candidate, expected, actual)
}
// now test every substring to stress test bounds checking
if !testing.Short() {
for start := 0; start < len(input); start++ {
for end := start + 1; end <= len(input); end++ {
candidate = input[start:end]
_ = runMarkdownBlock(candidate, extensions)
}
}
fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
}
}
}
func TestPrefixHeaderNoExtensions(t *testing.T) {
var tests = []string{
"# Header 1\n",
"<h1>Header 1</h1>\n",
"## Header 2\n",
"<h2>Header 2</h2>\n",
"### Header 3\n",
"<h3>Header 3</h3>\n",
"#### Header 4\n",
"<h4>Header 4</h4>\n",
"##### Header 5\n",
"<h5>Header 5</h5>\n",
"###### Header 6\n",
"<h6>Header 6</h6>\n",
"####### Header 7\n",
"<h6># Header 7</h6>\n",
"#Header 1\n",
"<h1>Header 1</h1>\n",
"##Header 2\n",
"<h2>Header 2</h2>\n",
"###Header 3\n",
"<h3>Header 3</h3>\n",
"####Header 4\n",
"<h4>Header 4</h4>\n",
"#####Header 5\n",
"<h5>Header 5</h5>\n",
"######Header 6\n",
"<h6>Header 6</h6>\n",
"#######Header 7\n",
"<h6>#Header 7</h6>\n",
"Hello\n# Header 1\nGoodbye\n",
"<p>Hello</p>\n\n<h1>Header 1</h1>\n\n<p>Goodbye</p>\n",
"* List\n# Header\n* List\n",
more consistent spacing of block-level elements
2011-07-02 01:19:42 +08:00
"<ul>\n<li><p>List</p>\n\n<h1>Header</h1></li>\n\n<li><p>List</p></li>\n</ul>\n",
fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
"* List\n#Header\n* List\n",
more consistent spacing of block-level elements
2011-07-02 01:19:42 +08:00
"<ul>\n<li><p>List</p>\n\n<h1>Header</h1></li>\n\n<li><p>List</p></li>\n</ul>\n",
fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
"* List\n * Nested list\n # Nested header\n",
"<ul>\n<li><p>List</p>\n\n<ul>\n<li><p>Nested list</p>\n\n" +
"<h1>Nested header</h1></li>\n</ul></li>\n</ul>\n",
Allow heading to end with \# The problem was in a loop that skipped the optional closing hashes in a heading like this: ### This is an H3 ### Now it checks to see if a hash is escaped and if it is, treats it as a rightmost character of the heading text, like this: ### This is an H3 #\## ==> ### This is an H3 ## Fixes issue #146.
2015-04-08 02:12:29 +08:00
"#Header 1 \\#\n",
"<h1>Header 1 #</h1>\n",
"#Header 1 \\# foo\n",
"<h1>Header 1 # foo</h1>\n",
"#Header 1 #\\##\n",
"<h1>Header 1 ##</h1>\n",
fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
}
doTestsBlock(t, tests, 0)
}
func TestPrefixHeaderSpaceExtension(t *testing.T) {
var tests = []string{
"# Header 1\n",
"<h1>Header 1</h1>\n",
"## Header 2\n",
"<h2>Header 2</h2>\n",
"### Header 3\n",
"<h3>Header 3</h3>\n",
"#### Header 4\n",
"<h4>Header 4</h4>\n",
"##### Header 5\n",
"<h5>Header 5</h5>\n",
"###### Header 6\n",
"<h6>Header 6</h6>\n",
"####### Header 7\n",
"<p>####### Header 7</p>\n",
"#Header 1\n",
"<p>#Header 1</p>\n",
"##Header 2\n",
"<p>##Header 2</p>\n",
"###Header 3\n",
"<p>###Header 3</p>\n",
"####Header 4\n",
"<p>####Header 4</p>\n",
"#####Header 5\n",
"<p>#####Header 5</p>\n",
"######Header 6\n",
"<p>######Header 6</p>\n",
"#######Header 7\n",
"<p>#######Header 7</p>\n",
"Hello\n# Header 1\nGoodbye\n",
"<p>Hello</p>\n\n<h1>Header 1</h1>\n\n<p>Goodbye</p>\n",
"* List\n# Header\n* List\n",
more consistent spacing of block-level elements
2011-07-02 01:19:42 +08:00
"<ul>\n<li><p>List</p>\n\n<h1>Header</h1></li>\n\n<li><p>List</p></li>\n</ul>\n",
fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
"* List\n#Header\n* List\n",
"<ul>\n<li>List\n#Header</li>\n<li>List</li>\n</ul>\n",
"* List\n * Nested list\n # Nested header\n",
"<ul>\n<li><p>List</p>\n\n<ul>\n<li><p>Nested list</p>\n\n" +
"<h1>Nested header</h1></li>\n</ul></li>\n</ul>\n",
unit tests for underlined headers, improved whitespace handling for the same
2011-06-28 01:42:38 +08:00
}
doTestsBlock(t, tests, EXTENSION_SPACE_HEADERS)
}
Add header ID support and tests: # Header {#myid}
2014-04-06 03:42:58 +08:00
func TestPrefixHeaderIdExtension(t *testing.T) {
var tests = []string{
"# Header 1 {#someid}\n",
"<h1 id=\"someid\">Header 1</h1>\n",
"# Header 1 {#someid} \n",
"<h1 id=\"someid\">Header 1</h1>\n",
"# Header 1 {#someid}\n",
"<h1 id=\"someid\">Header 1</h1>\n",
"# Header 1 {#someid\n",
"<h1>Header 1 {#someid</h1>\n",
Correctly emit trailing header ID brace
2014-04-06 03:59:03 +08:00
"# Header 1 {#someid\n",
"<h1>Header 1 {#someid</h1>\n",
"# Header 1 {#someid}}\n",
"<h1 id=\"someid\">Header 1</h1>\n\n<p>}</p>\n",
Add header ID support and tests: # Header {#myid}
2014-04-06 03:42:58 +08:00
"## Header 2 {#someid}\n",
"<h2 id=\"someid\">Header 2</h2>\n",
"### Header 3 {#someid}\n",
"<h3 id=\"someid\">Header 3</h3>\n",
"#### Header 4 {#someid}\n",
"<h4 id=\"someid\">Header 4</h4>\n",
"##### Header 5 {#someid}\n",
"<h5 id=\"someid\">Header 5</h5>\n",
"###### Header 6 {#someid}\n",
"<h6 id=\"someid\">Header 6</h6>\n",
"####### Header 7 {#someid}\n",
"<h6 id=\"someid\"># Header 7</h6>\n",
Also support header IDs in ## headers ##
2014-04-06 17:30:40 +08:00
"# Header 1 # {#someid}\n",
"<h1 id=\"someid\">Header 1</h1>\n",
"## Header 2 ## {#someid}\n",
"<h2 id=\"someid\">Header 2</h2>\n",
Add header ID support and tests: # Header {#myid}
2014-04-06 03:42:58 +08:00
"Hello\n# Header 1\nGoodbye\n",
"<p>Hello</p>\n\n<h1>Header 1</h1>\n\n<p>Goodbye</p>\n",
"* List\n# Header {#someid}\n* List\n",
"<ul>\n<li><p>List</p>\n\n<h1 id=\"someid\">Header</h1></li>\n\n<li><p>List</p></li>\n</ul>\n",
"* List\n#Header {#someid}\n* List\n",
"<ul>\n<li><p>List</p>\n\n<h1 id=\"someid\">Header</h1></li>\n\n<li><p>List</p></li>\n</ul>\n",
"* List\n * Nested list\n # Nested header {#someid}\n",
"<ul>\n<li><p>List</p>\n\n<ul>\n<li><p>Nested list</p>\n\n" +
"<h1 id=\"someid\">Nested header</h1></li>\n</ul></li>\n</ul>\n",
}
doTestsBlock(t, tests, EXTENSION_HEADER_IDS)
}
Allow configurable header ID prefix/suffixes. This is specifically driven by the Hugo usecase where multiple documents are often rendered into the same ultimate HTML page. When a header ID is written to the output HTML format (either through `HTML_TOC`, `EXTENSION_HEADER_IDS`, or `EXTENSION_AUTO_HEADER_IDS`), it is possible that multiple documents will hvae identical header IDs. To permit validation to pass, it is useful to have a per-document prefix or suffix (in our case, an MD5 of the content filename, and we will be using it as a suffix). That is, two documents (`A` and `B`) that have the same header ID (`# Reason {#reason}`), will end up having an actual header ID of the form `#reason-DOCID` (e.g., `#reason-A`, `#reason-B`) with these HTML parameters. This is built on top of #126 (more intelligent collision detection for `EXTENSION_AUTO_HEADER_IDS`).
2014-11-24 09:37:27 +08:00
func TestPrefixHeaderIdExtensionWithPrefixAndSuffix(t *testing.T) {
var tests = []string{
"# header 1 {#someid}\n",
"<h1 id=\"PRE:someid:POST\">header 1</h1>\n",
"## header 2 {#someid}\n",
"<h2 id=\"PRE:someid:POST\">header 2</h2>\n",
"### header 3 {#someid}\n",
"<h3 id=\"PRE:someid:POST\">header 3</h3>\n",
"#### header 4 {#someid}\n",
"<h4 id=\"PRE:someid:POST\">header 4</h4>\n",
"##### header 5 {#someid}\n",
"<h5 id=\"PRE:someid:POST\">header 5</h5>\n",
"###### header 6 {#someid}\n",
"<h6 id=\"PRE:someid:POST\">header 6</h6>\n",
"####### header 7 {#someid}\n",
"<h6 id=\"PRE:someid:POST\"># header 7</h6>\n",
"# header 1 # {#someid}\n",
"<h1 id=\"PRE:someid:POST\">header 1</h1>\n",
"## header 2 ## {#someid}\n",
"<h2 id=\"PRE:someid:POST\">header 2</h2>\n",
"* List\n# Header {#someid}\n* List\n",
"<ul>\n<li><p>List</p>\n\n<h1 id=\"PRE:someid:POST\">Header</h1></li>\n\n<li><p>List</p></li>\n</ul>\n",
"* List\n#Header {#someid}\n* List\n",
"<ul>\n<li><p>List</p>\n\n<h1 id=\"PRE:someid:POST\">Header</h1></li>\n\n<li><p>List</p></li>\n</ul>\n",
"* List\n * Nested list\n # Nested header {#someid}\n",
"<ul>\n<li><p>List</p>\n\n<ul>\n<li><p>Nested list</p>\n\n" +
"<h1 id=\"PRE:someid:POST\">Nested header</h1></li>\n</ul></li>\n</ul>\n",
}
parameters := HtmlRendererParameters{
HeaderIDPrefix: "PRE:",
HeaderIDSuffix: ":POST",
}
doTestsBlockWithRunner(t, tests, EXTENSION_HEADER_IDS, runnerWithRendererParameters(parameters))
}
Add a flag to turn on header ID generation. - Fixes #51, #101, and #102. - Uses the [code][gfm] mentioned by @shurcooL from his Github Flavored Markdown parser extension in a [comment on #102][comment]. Since this was mentioned, I assumed that @shurcooL would be OK with this being included under the licence provided by blackfriday (there is no licence comment on his code). - I’ve added it behind another flag, EXTENSION_AUTO_HEADER_IDS, that would need to be turned on for it to work. It works with both prefix and underline headers. [gfm]: https://github.com/shurcooL/go/blob/3bec0366a85101d116bf88b477e92ea6cdd75e4e/github_flavored_markdown/main.go#L90-L102 [comment]: https://github.com/russross/blackfriday/issues/102#issuecomment-51272260
2014-10-28 04:54:23 +08:00
func TestPrefixAutoHeaderIdExtension(t *testing.T) {
var tests = []string{
"# Header 1\n",
"<h1 id=\"header-1\">Header 1</h1>\n",
"# Header 1 \n",
"<h1 id=\"header-1\">Header 1</h1>\n",
"## Header 2\n",
"<h2 id=\"header-2\">Header 2</h2>\n",
"### Header 3\n",
"<h3 id=\"header-3\">Header 3</h3>\n",
"#### Header 4\n",
"<h4 id=\"header-4\">Header 4</h4>\n",
"##### Header 5\n",
"<h5 id=\"header-5\">Header 5</h5>\n",
"###### Header 6\n",
"<h6 id=\"header-6\">Header 6</h6>\n",
"####### Header 7\n",
Fix test case. Fix a minor issue in expected anchor after recent PR. The tests were written before the improvement that squashes non-alphanumeric characters into a single dash, and does not include dashes at the beginning and end. This updates the test case to match that behavior so that tests pass and Travis is green.
2014-11-25 12:01:03 +08:00
"<h6 id=\"header-7\"># Header 7</h6>\n",
Add a flag to turn on header ID generation. - Fixes #51, #101, and #102. - Uses the [code][gfm] mentioned by @shurcooL from his Github Flavored Markdown parser extension in a [comment on #102][comment]. Since this was mentioned, I assumed that @shurcooL would be OK with this being included under the licence provided by blackfriday (there is no licence comment on his code). - I’ve added it behind another flag, EXTENSION_AUTO_HEADER_IDS, that would need to be turned on for it to work. It works with both prefix and underline headers. [gfm]: https://github.com/shurcooL/go/blob/3bec0366a85101d116bf88b477e92ea6cdd75e4e/github_flavored_markdown/main.go#L90-L102 [comment]: https://github.com/russross/blackfriday/issues/102#issuecomment-51272260
2014-10-28 04:54:23 +08:00
"Hello\n# Header 1\nGoodbye\n",
"<p>Hello</p>\n\n<h1 id=\"header-1\">Header 1</h1>\n\n<p>Goodbye</p>\n",
"* List\n# Header\n* List\n",
"<ul>\n<li><p>List</p>\n\n<h1 id=\"header\">Header</h1></li>\n\n<li><p>List</p></li>\n</ul>\n",
"* List\n#Header\n* List\n",
"<ul>\n<li><p>List</p>\n\n<h1 id=\"header\">Header</h1></li>\n\n<li><p>List</p></li>\n</ul>\n",
"* List\n * Nested list\n # Nested header\n",
"<ul>\n<li><p>List</p>\n\n<ul>\n<li><p>Nested list</p>\n\n" +
"<h1 id=\"nested-header\">Nested header</h1></li>\n</ul></li>\n</ul>\n",
Prevent generated header collisions, less naively. > This is a rework of an earlier version of this code. The automatic header ID generation code submitted in #125 has a subtle bug where it will use the same ID for multiple headers with identical text. In the case below, all the headers are rendered a `<h1 id="header">Header</h1>`. ```markdown # Header # Header # Header # Header ``` This change is a simple but robust approach that uses an incrementing counter and pre-checking to prevent header collision. (The above would be rendered as `header`, `header-1`, `header-2`, and `header-3`.) In more complex cases, it will append a new counter suffix (`-1`), like so: ```markdown # Header # Header 1 # Header # Header ``` This will generate `header`, `header-1`, `header-1-1`, and `header-1-2`. This code has two additional changes over the prior version: 1. Rather than reimplementing @shurcooL’s anchor sanitization code, I have imported it as from `github.com/shurcooL/go/github_flavored_markdown/sanitized_anchor_name`. 2. The markdown block parser is now only interested in *generating* a sanitized anchor name, not with ensuring its uniqueness. That code has been moved to the HTML renderer. This means that if the HTML renderer is modified to identify all unique headers prior to rendering, the hackish nature of the collision detection can be eliminated.
2014-11-02 06:35:35 +08:00
"# Header\n\n# Header\n",
"<h1 id=\"header\">Header</h1>\n\n<h1 id=\"header-1\">Header</h1>\n",
"# Header 1\n\n# Header 1",
"<h1 id=\"header-1\">Header 1</h1>\n\n<h1 id=\"header-1-1\">Header 1</h1>\n",
"# Header\n\n# Header 1\n\n# Header\n\n# Header",
"<h1 id=\"header\">Header</h1>\n\n<h1 id=\"header-1\">Header 1</h1>\n\n<h1 id=\"header-1-1\">Header</h1>\n\n<h1 id=\"header-1-2\">Header</h1>\n",
Add a flag to turn on header ID generation. - Fixes #51, #101, and #102. - Uses the [code][gfm] mentioned by @shurcooL from his Github Flavored Markdown parser extension in a [comment on #102][comment]. Since this was mentioned, I assumed that @shurcooL would be OK with this being included under the licence provided by blackfriday (there is no licence comment on his code). - I’ve added it behind another flag, EXTENSION_AUTO_HEADER_IDS, that would need to be turned on for it to work. It works with both prefix and underline headers. [gfm]: https://github.com/shurcooL/go/blob/3bec0366a85101d116bf88b477e92ea6cdd75e4e/github_flavored_markdown/main.go#L90-L102 [comment]: https://github.com/russross/blackfriday/issues/102#issuecomment-51272260
2014-10-28 04:54:23 +08:00
}
doTestsBlock(t, tests, EXTENSION_AUTO_HEADER_IDS)
}
Allow configurable header ID prefix/suffixes. This is specifically driven by the Hugo usecase where multiple documents are often rendered into the same ultimate HTML page. When a header ID is written to the output HTML format (either through `HTML_TOC`, `EXTENSION_HEADER_IDS`, or `EXTENSION_AUTO_HEADER_IDS`), it is possible that multiple documents will hvae identical header IDs. To permit validation to pass, it is useful to have a per-document prefix or suffix (in our case, an MD5 of the content filename, and we will be using it as a suffix). That is, two documents (`A` and `B`) that have the same header ID (`# Reason {#reason}`), will end up having an actual header ID of the form `#reason-DOCID` (e.g., `#reason-A`, `#reason-B`) with these HTML parameters. This is built on top of #126 (more intelligent collision detection for `EXTENSION_AUTO_HEADER_IDS`).
2014-11-24 09:37:27 +08:00
func TestPrefixAutoHeaderIdExtensionWithPrefixAndSuffix(t *testing.T) {
var tests = []string{
"# Header 1\n",
"<h1 id=\"PRE:header-1:POST\">Header 1</h1>\n",
"# Header 1 \n",
"<h1 id=\"PRE:header-1:POST\">Header 1</h1>\n",
"## Header 2\n",
"<h2 id=\"PRE:header-2:POST\">Header 2</h2>\n",
"### Header 3\n",
"<h3 id=\"PRE:header-3:POST\">Header 3</h3>\n",
"#### Header 4\n",
"<h4 id=\"PRE:header-4:POST\">Header 4</h4>\n",
"##### Header 5\n",
"<h5 id=\"PRE:header-5:POST\">Header 5</h5>\n",
"###### Header 6\n",
"<h6 id=\"PRE:header-6:POST\">Header 6</h6>\n",
"####### Header 7\n",
Fix test case. Fix a minor issue in expected anchor after recent PR. The tests were written before the improvement that squashes non-alphanumeric characters into a single dash, and does not include dashes at the beginning and end. This updates the test case to match that behavior so that tests pass and Travis is green.
2014-11-25 12:01:03 +08:00
"<h6 id=\"PRE:header-7:POST\"># Header 7</h6>\n",
Allow configurable header ID prefix/suffixes. This is specifically driven by the Hugo usecase where multiple documents are often rendered into the same ultimate HTML page. When a header ID is written to the output HTML format (either through `HTML_TOC`, `EXTENSION_HEADER_IDS`, or `EXTENSION_AUTO_HEADER_IDS`), it is possible that multiple documents will hvae identical header IDs. To permit validation to pass, it is useful to have a per-document prefix or suffix (in our case, an MD5 of the content filename, and we will be using it as a suffix). That is, two documents (`A` and `B`) that have the same header ID (`# Reason {#reason}`), will end up having an actual header ID of the form `#reason-DOCID` (e.g., `#reason-A`, `#reason-B`) with these HTML parameters. This is built on top of #126 (more intelligent collision detection for `EXTENSION_AUTO_HEADER_IDS`).
2014-11-24 09:37:27 +08:00
"Hello\n# Header 1\nGoodbye\n",
"<p>Hello</p>\n\n<h1 id=\"PRE:header-1:POST\">Header 1</h1>\n\n<p>Goodbye</p>\n",
"* List\n# Header\n* List\n",
"<ul>\n<li><p>List</p>\n\n<h1 id=\"PRE:header:POST\">Header</h1></li>\n\n<li><p>List</p></li>\n</ul>\n",
"* List\n#Header\n* List\n",
"<ul>\n<li><p>List</p>\n\n<h1 id=\"PRE:header:POST\">Header</h1></li>\n\n<li><p>List</p></li>\n</ul>\n",
"* List\n * Nested list\n # Nested header\n",
"<ul>\n<li><p>List</p>\n\n<ul>\n<li><p>Nested list</p>\n\n" +
"<h1 id=\"PRE:nested-header:POST\">Nested header</h1></li>\n</ul></li>\n</ul>\n",
"# Header\n\n# Header\n",
"<h1 id=\"PRE:header:POST\">Header</h1>\n\n<h1 id=\"PRE:header-1:POST\">Header</h1>\n",
"# Header 1\n\n# Header 1",
"<h1 id=\"PRE:header-1:POST\">Header 1</h1>\n\n<h1 id=\"PRE:header-1-1:POST\">Header 1</h1>\n",
"# Header\n\n# Header 1\n\n# Header\n\n# Header",
"<h1 id=\"PRE:header:POST\">Header</h1>\n\n<h1 id=\"PRE:header-1:POST\">Header 1</h1>\n\n<h1 id=\"PRE:header-1-1:POST\">Header</h1>\n\n<h1 id=\"PRE:header-1-2:POST\">Header</h1>\n",
}
parameters := HtmlRendererParameters{
HeaderIDPrefix: "PRE:",
HeaderIDSuffix: ":POST",
}
doTestsBlockWithRunner(t, tests, EXTENSION_AUTO_HEADER_IDS, runnerWithRendererParameters(parameters))
}
Prevent generated header collisions, less naively. > This is a rework of an earlier version of this code. The automatic header ID generation code submitted in #125 has a subtle bug where it will use the same ID for multiple headers with identical text. In the case below, all the headers are rendered a `<h1 id="header">Header</h1>`. ```markdown # Header # Header # Header # Header ``` This change is a simple but robust approach that uses an incrementing counter and pre-checking to prevent header collision. (The above would be rendered as `header`, `header-1`, `header-2`, and `header-3`.) In more complex cases, it will append a new counter suffix (`-1`), like so: ```markdown # Header # Header 1 # Header # Header ``` This will generate `header`, `header-1`, `header-1-1`, and `header-1-2`. This code has two additional changes over the prior version: 1. Rather than reimplementing @shurcooL’s anchor sanitization code, I have imported it as from `github.com/shurcooL/go/github_flavored_markdown/sanitized_anchor_name`. 2. The markdown block parser is now only interested in *generating* a sanitized anchor name, not with ensuring its uniqueness. That code has been moved to the HTML renderer. This means that if the HTML renderer is modified to identify all unique headers prior to rendering, the hackish nature of the collision detection can be eliminated.
2014-11-02 06:35:35 +08:00
func TestPrefixMultipleHeaderExtensions(t *testing.T) {
var tests = []string{
"# Header\n\n# Header {#header}\n\n# Header 1",
"<h1 id=\"header\">Header</h1>\n\n<h1 id=\"header-1\">Header</h1>\n\n<h1 id=\"header-1-1\">Header 1</h1>\n",
}
doTestsBlock(t, tests, EXTENSION_AUTO_HEADER_IDS|EXTENSION_HEADER_IDS)
}
unit tests for underlined headers, improved whitespace handling for the same
2011-06-28 01:42:38 +08:00
func TestUnderlineHeaders(t *testing.T) {
var tests = []string{
"Header 1\n========\n",
"<h1>Header 1</h1>\n",
"Header 2\n--------\n",
"<h2>Header 2</h2>\n",
"A\n=\n",
"<h1>A</h1>\n",
"B\n-\n",
"<h2>B</h2>\n",
"Paragraph\nHeader\n=\n",
"<p>Paragraph</p>\n\n<h1>Header</h1>\n",
"Header\n===\nParagraph\n",
"<h1>Header</h1>\n\n<p>Paragraph</p>\n",
"Header\n===\nAnother header\n---\n",
"<h1>Header</h1>\n\n<h2>Another header</h2>\n",
" Header\n======\n",
"<h1>Header</h1>\n",
" Code\n========\n",
"<pre><code>Code\n</code></pre>\n\n<p>========</p>\n",
"Header with *inline*\n=====\n",
"<h1>Header with <em>inline</em></h1>\n",
fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
"* List\n * Sublist\n Not a header\n ------\n",
"<ul>\n<li>List\n\n<ul>\n<li>Sublist\nNot a header\n------</li>\n</ul></li>\n</ul>\n",
unit tests for underlined headers, improved whitespace handling for the same
2011-06-28 01:42:38 +08:00
"Paragraph\n\n\n\n\nHeader\n===\n",
"<p>Paragraph</p>\n\n<h1>Header</h1>\n",
"Trailing space \n==== \n\n",
"<h1>Trailing space</h1>\n",
"Trailing spaces\n==== \n\n",
"<h1>Trailing spaces</h1>\n",
fixed minor bugs uncovered by more testing
2011-06-28 04:35:11 +08:00
"Double underline\n=====\n=====\n",
"<h1>Double underline</h1>\n\n<p>=====</p>\n",
fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
}
unit tests for underlined headers, improved whitespace handling for the same
2011-06-28 01:42:38 +08:00
doTestsBlock(t, tests, 0)
fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
}
horizontal rule and list testing
2011-06-28 06:06:32 +08:00
Add a flag to turn on header ID generation. - Fixes #51, #101, and #102. - Uses the [code][gfm] mentioned by @shurcooL from his Github Flavored Markdown parser extension in a [comment on #102][comment]. Since this was mentioned, I assumed that @shurcooL would be OK with this being included under the licence provided by blackfriday (there is no licence comment on his code). - I’ve added it behind another flag, EXTENSION_AUTO_HEADER_IDS, that would need to be turned on for it to work. It works with both prefix and underline headers. [gfm]: https://github.com/shurcooL/go/blob/3bec0366a85101d116bf88b477e92ea6cdd75e4e/github_flavored_markdown/main.go#L90-L102 [comment]: https://github.com/russross/blackfriday/issues/102#issuecomment-51272260
2014-10-28 04:54:23 +08:00
func TestUnderlineHeadersAutoIDs(t *testing.T) {
var tests = []string{
"Header 1\n========\n",
"<h1 id=\"header-1\">Header 1</h1>\n",
"Header 2\n--------\n",
"<h2 id=\"header-2\">Header 2</h2>\n",
"A\n=\n",
"<h1 id=\"a\">A</h1>\n",
"B\n-\n",
"<h2 id=\"b\">B</h2>\n",
"Paragraph\nHeader\n=\n",
"<p>Paragraph</p>\n\n<h1 id=\"header\">Header</h1>\n",
"Header\n===\nParagraph\n",
"<h1 id=\"header\">Header</h1>\n\n<p>Paragraph</p>\n",
"Header\n===\nAnother header\n---\n",
"<h1 id=\"header\">Header</h1>\n\n<h2 id=\"another-header\">Another header</h2>\n",
" Header\n======\n",
"<h1 id=\"header\">Header</h1>\n",
"Header with *inline*\n=====\n",
"<h1 id=\"header-with-inline\">Header with <em>inline</em></h1>\n",
"Paragraph\n\n\n\n\nHeader\n===\n",
"<p>Paragraph</p>\n\n<h1 id=\"header\">Header</h1>\n",
"Trailing space \n==== \n\n",
"<h1 id=\"trailing-space\">Trailing space</h1>\n",
"Trailing spaces\n==== \n\n",
"<h1 id=\"trailing-spaces\">Trailing spaces</h1>\n",
"Double underline\n=====\n=====\n",
"<h1 id=\"double-underline\">Double underline</h1>\n\n<p>=====</p>\n",
Prevent generated header collisions, less naively. > This is a rework of an earlier version of this code. The automatic header ID generation code submitted in #125 has a subtle bug where it will use the same ID for multiple headers with identical text. In the case below, all the headers are rendered a `<h1 id="header">Header</h1>`. ```markdown # Header # Header # Header # Header ``` This change is a simple but robust approach that uses an incrementing counter and pre-checking to prevent header collision. (The above would be rendered as `header`, `header-1`, `header-2`, and `header-3`.) In more complex cases, it will append a new counter suffix (`-1`), like so: ```markdown # Header # Header 1 # Header # Header ``` This will generate `header`, `header-1`, `header-1-1`, and `header-1-2`. This code has two additional changes over the prior version: 1. Rather than reimplementing @shurcooL’s anchor sanitization code, I have imported it as from `github.com/shurcooL/go/github_flavored_markdown/sanitized_anchor_name`. 2. The markdown block parser is now only interested in *generating* a sanitized anchor name, not with ensuring its uniqueness. That code has been moved to the HTML renderer. This means that if the HTML renderer is modified to identify all unique headers prior to rendering, the hackish nature of the collision detection can be eliminated.
2014-11-02 06:35:35 +08:00
"Header\n======\n\nHeader\n======\n",
"<h1 id=\"header\">Header</h1>\n\n<h1 id=\"header-1\">Header</h1>\n",
"Header 1\n========\n\nHeader 1\n========\n",
"<h1 id=\"header-1\">Header 1</h1>\n\n<h1 id=\"header-1-1\">Header 1</h1>\n",
Add a flag to turn on header ID generation. - Fixes #51, #101, and #102. - Uses the [code][gfm] mentioned by @shurcooL from his Github Flavored Markdown parser extension in a [comment on #102][comment]. Since this was mentioned, I assumed that @shurcooL would be OK with this being included under the licence provided by blackfriday (there is no licence comment on his code). - I’ve added it behind another flag, EXTENSION_AUTO_HEADER_IDS, that would need to be turned on for it to work. It works with both prefix and underline headers. [gfm]: https://github.com/shurcooL/go/blob/3bec0366a85101d116bf88b477e92ea6cdd75e4e/github_flavored_markdown/main.go#L90-L102 [comment]: https://github.com/russross/blackfriday/issues/102#issuecomment-51272260
2014-10-28 04:54:23 +08:00
}
doTestsBlock(t, tests, EXTENSION_AUTO_HEADER_IDS)
}
horizontal rule and list testing
2011-06-28 06:06:32 +08:00
func TestHorizontalRule(t *testing.T) {
var tests = []string{
"-\n",
"<p>-</p>\n",
"--\n",
"<p>--</p>\n",
"---\n",
"<hr />\n",
"----\n",
"<hr />\n",
"*\n",
"<p>*</p>\n",
"**\n",
"<p>**</p>\n",
"***\n",
"<hr />\n",
"****\n",
"<hr />\n",
"_\n",
"<p>_</p>\n",
"__\n",
"<p>__</p>\n",
"___\n",
"<hr />\n",
"____\n",
"<hr />\n",
"-*-\n",
"<p>-*-</p>\n",
"- - -\n",
"<hr />\n",
"* * *\n",
"<hr />\n",
"_ _ _\n",
"<hr />\n",
"-----*\n",
"<p>-----*</p>\n",
" ------ \n",
"<hr />\n",
"Hello\n***\n",
"<p>Hello</p>\n\n<hr />\n",
"---\n***\n___\n",
"<hr />\n\n<hr />\n\n<hr />\n",
}
doTestsBlock(t, tests, 0)
}
func TestUnorderedList(t *testing.T) {
var tests = []string{
"* Hello\n",
"<ul>\n<li>Hello</li>\n</ul>\n",
"* Yin\n* Yang\n",
"<ul>\n<li>Yin</li>\n<li>Yang</li>\n</ul>\n",
"* Ting\n* Bong\n* Goo\n",
"<ul>\n<li>Ting</li>\n<li>Bong</li>\n<li>Goo</li>\n</ul>\n",
"* Yin\n\n* Yang\n",
more consistent spacing of block-level elements
2011-07-02 01:19:42 +08:00
"<ul>\n<li><p>Yin</p></li>\n\n<li><p>Yang</p></li>\n</ul>\n",
horizontal rule and list testing
2011-06-28 06:06:32 +08:00
"* Ting\n\n* Bong\n* Goo\n",
more consistent spacing of block-level elements
2011-07-02 01:19:42 +08:00
"<ul>\n<li><p>Ting</p></li>\n\n<li><p>Bong</p></li>\n\n<li><p>Goo</p></li>\n</ul>\n",
horizontal rule and list testing
2011-06-28 06:06:32 +08:00
"+ Hello\n",
"<ul>\n<li>Hello</li>\n</ul>\n",
"+ Yin\n+ Yang\n",
"<ul>\n<li>Yin</li>\n<li>Yang</li>\n</ul>\n",
"+ Ting\n+ Bong\n+ Goo\n",
"<ul>\n<li>Ting</li>\n<li>Bong</li>\n<li>Goo</li>\n</ul>\n",
"+ Yin\n\n+ Yang\n",
more consistent spacing of block-level elements
2011-07-02 01:19:42 +08:00
"<ul>\n<li><p>Yin</p></li>\n\n<li><p>Yang</p></li>\n</ul>\n",
horizontal rule and list testing
2011-06-28 06:06:32 +08:00
"+ Ting\n\n+ Bong\n+ Goo\n",
more consistent spacing of block-level elements
2011-07-02 01:19:42 +08:00
"<ul>\n<li><p>Ting</p></li>\n\n<li><p>Bong</p></li>\n\n<li><p>Goo</p></li>\n</ul>\n",
horizontal rule and list testing
2011-06-28 06:06:32 +08:00
"- Hello\n",
"<ul>\n<li>Hello</li>\n</ul>\n",
"- Yin\n- Yang\n",
"<ul>\n<li>Yin</li>\n<li>Yang</li>\n</ul>\n",
"- Ting\n- Bong\n- Goo\n",
"<ul>\n<li>Ting</li>\n<li>Bong</li>\n<li>Goo</li>\n</ul>\n",
"- Yin\n\n- Yang\n",
more consistent spacing of block-level elements
2011-07-02 01:19:42 +08:00
"<ul>\n<li><p>Yin</p></li>\n\n<li><p>Yang</p></li>\n</ul>\n",
horizontal rule and list testing
2011-06-28 06:06:32 +08:00
"- Ting\n\n- Bong\n- Goo\n",
more consistent spacing of block-level elements
2011-07-02 01:19:42 +08:00
"<ul>\n<li><p>Ting</p></li>\n\n<li><p>Bong</p></li>\n\n<li><p>Goo</p></li>\n</ul>\n",
horizontal rule and list testing
2011-06-28 06:06:32 +08:00
"*Hello\n",
"<p>*Hello</p>\n",
"* Hello \n",
"<ul>\n<li>Hello</li>\n</ul>\n",
"* Hello \n Next line \n",
"<ul>\n<li>Hello\nNext line</li>\n</ul>\n",
"Paragraph\n* No linebreak\n",
"<p>Paragraph\n* No linebreak</p>\n",
"Paragraph\n\n* Linebreak\n",
"<p>Paragraph</p>\n\n<ul>\n<li>Linebreak</li>\n</ul>\n",
Fix adjacent list merging Prevent adjacent lists of differing types from being merged into a single list. No options are provided to enable the previous behavior. Fixes #235
2016-05-02 21:54:19 +08:00
"* List\n\n1. Spacer Mixed listing\n",
"<ul>\n<li>List</li>\n</ul>\n\n<ol>\n<li>Spacer Mixed listing</li>\n</ol>\n",
horizontal rule and list testing
2011-06-28 06:06:32 +08:00
"* List\n * Nested list\n",
"<ul>\n<li>List\n\n<ul>\n<li>Nested list</li>\n</ul></li>\n</ul>\n",
"* List\n\n * Nested list\n",
"<ul>\n<li><p>List</p>\n\n<ul>\n<li>Nested list</li>\n</ul></li>\n</ul>\n",
"* List\n Second line\n\n + Nested\n",
"<ul>\n<li><p>List\nSecond line</p>\n\n<ul>\n<li>Nested</li>\n</ul></li>\n</ul>\n",
"* List\n + Nested\n\n Continued\n",
"<ul>\n<li><p>List</p>\n\n<ul>\n<li>Nested</li>\n</ul>\n\n<p>Continued</p></li>\n</ul>\n",
"* List\n * shallow indent\n",
"<ul>\n<li>List\n\n<ul>\n<li>shallow indent</li>\n</ul></li>\n</ul>\n",
"* List\n" +
" * shallow indent\n" +
" * part of second list\n" +
" * still second\n" +
" * almost there\n" +
" * third level\n",
"<ul>\n" +
"<li>List\n\n" +
"<ul>\n" +
"<li>shallow indent</li>\n" +
"<li>part of second list</li>\n" +
"<li>still second</li>\n" +
"<li>almost there\n\n" +
"<ul>\n" +
"<li>third level</li>\n" +
"</ul></li>\n" +
"</ul></li>\n" +
"</ul>\n",
tests for ordered lists
2011-06-28 08:03:54 +08:00
"* List\n extra indent, same paragraph\n",
"<ul>\n<li>List\n extra indent, same paragraph</li>\n</ul>\n",
"* List\n\n code block\n",
"<ul>\n<li><p>List</p>\n\n<pre><code>code block\n</code></pre></li>\n</ul>\n",
"* List\n\n code block with spaces\n",
"<ul>\n<li><p>List</p>\n\n<pre><code> code block with spaces\n</code></pre></li>\n</ul>\n",
fixed bug with blank line handling within list items
2011-09-10 02:30:45 +08:00
"* List\n\n * sublist\n\n normal text\n\n * another sublist\n",
"<ul>\n<li><p>List</p>\n\n<ul>\n<li>sublist</li>\n</ul>\n\n<p>normal text</p>\n\n<ul>\n<li>another sublist</li>\n</ul></li>\n</ul>\n",
Fix bug with gathering list item lines Instead of swallowing an empty line and then reintroducing it back again in certain cases, collect the list item body in an unaltered form and let the recursive parsing call sort things out. Fixes issue #228.
2015-12-27 02:18:22 +08:00
`* Foo
bar
qux
`,
`<ul>
<li><p>Foo</p>
<pre><code>bar
qux
</code></pre></li>
</ul>
`,
tests for ordered lists
2011-06-28 08:03:54 +08:00
}
doTestsBlock(t, tests, 0)
}
Fix bug with gathering list item lines Instead of swallowing an empty line and then reintroducing it back again in certain cases, collect the list item body in an unaltered form and let the recursive parsing call sort things out. Fixes issue #228.
2015-12-27 02:18:22 +08:00
func TestFencedCodeBlockWithinList(t *testing.T) {
doTestsBlock(t, []string{
"* Foo\n\n ```\n bar\n\n qux\n ```\n",
`<ul>
<li><p>Foo</p>
<pre><code>bar
qux
</code></pre></li>
</ul>
`,
}, EXTENSION_FENCED_CODE)
}
tests for ordered lists
2011-06-28 08:03:54 +08:00
func TestOrderedList(t *testing.T) {
var tests = []string{
"1. Hello\n",
"<ol>\n<li>Hello</li>\n</ol>\n",
"1. Yin\n2. Yang\n",
"<ol>\n<li>Yin</li>\n<li>Yang</li>\n</ol>\n",
"1. Ting\n2. Bong\n3. Goo\n",
"<ol>\n<li>Ting</li>\n<li>Bong</li>\n<li>Goo</li>\n</ol>\n",
"1. Yin\n\n2. Yang\n",
more consistent spacing of block-level elements
2011-07-02 01:19:42 +08:00
"<ol>\n<li><p>Yin</p></li>\n\n<li><p>Yang</p></li>\n</ol>\n",
tests for ordered lists
2011-06-28 08:03:54 +08:00
"1. Ting\n\n2. Bong\n3. Goo\n",
more consistent spacing of block-level elements
2011-07-02 01:19:42 +08:00
"<ol>\n<li><p>Ting</p></li>\n\n<li><p>Bong</p></li>\n\n<li><p>Goo</p></li>\n</ol>\n",
tests for ordered lists
2011-06-28 08:03:54 +08:00
"1 Hello\n",
"<p>1 Hello</p>\n",
"1.Hello\n",
"<p>1.Hello</p>\n",
"1. Hello \n",
"<ol>\n<li>Hello</li>\n</ol>\n",
"1. Hello \n Next line \n",
"<ol>\n<li>Hello\nNext line</li>\n</ol>\n",
"Paragraph\n1. No linebreak\n",
"<p>Paragraph\n1. No linebreak</p>\n",
"Paragraph\n\n1. Linebreak\n",
"<p>Paragraph</p>\n\n<ol>\n<li>Linebreak</li>\n</ol>\n",
"1. List\n 1. Nested list\n",
"<ol>\n<li>List\n\n<ol>\n<li>Nested list</li>\n</ol></li>\n</ol>\n",
"1. List\n\n 1. Nested list\n",
"<ol>\n<li><p>List</p>\n\n<ol>\n<li>Nested list</li>\n</ol></li>\n</ol>\n",
"1. List\n Second line\n\n 1. Nested\n",
"<ol>\n<li><p>List\nSecond line</p>\n\n<ol>\n<li>Nested</li>\n</ol></li>\n</ol>\n",
"1. List\n 1. Nested\n\n Continued\n",
"<ol>\n<li><p>List</p>\n\n<ol>\n<li>Nested</li>\n</ol>\n\n<p>Continued</p></li>\n</ol>\n",
"1. List\n 1. shallow indent\n",
"<ol>\n<li>List\n\n<ol>\n<li>shallow indent</li>\n</ol></li>\n</ol>\n",
"1. List\n" +
" 1. shallow indent\n" +
" 2. part of second list\n" +
" 3. still second\n" +
" 4. almost there\n" +
" 1. third level\n",
"<ol>\n" +
"<li>List\n\n" +
"<ol>\n" +
"<li>shallow indent</li>\n" +
"<li>part of second list</li>\n" +
"<li>still second</li>\n" +
"<li>almost there\n\n" +
"<ol>\n" +
"<li>third level</li>\n" +
"</ol></li>\n" +
"</ol></li>\n" +
"</ol>\n",
"1. List\n extra indent, same paragraph\n",
"<ol>\n<li>List\n extra indent, same paragraph</li>\n</ol>\n",
"1. List\n\n code block\n",
"<ol>\n<li><p>List</p>\n\n<pre><code>code block\n</code></pre></li>\n</ol>\n",
"1. List\n\n code block with spaces\n",
"<ol>\n<li><p>List</p>\n\n<pre><code> code block with spaces\n</code></pre></li>\n</ol>\n",
Fix adjacent list merging Prevent adjacent lists of differing types from being merged into a single list. No options are provided to enable the previous behavior. Fixes #235
2016-05-02 21:54:19 +08:00
"1. List\n\n* Spacer Mixed listing\n",
"<ol>\n<li>List</li>\n</ol>\n\n<ul>\n<li>Spacer Mixed listing</li>\n</ul>\n",
"1. List\n* Mixed listing\n",
"<ol>\n<li>List</li>\n<li>Mixed listing</li>\n</ol>\n",
tests for ordered lists
2011-06-28 08:03:54 +08:00
"1. List\n * Mixted list\n",
"<ol>\n<li>List\n\n<ul>\n<li>Mixted list</li>\n</ul></li>\n</ol>\n",
"1. List\n * Mixed list\n",
"<ol>\n<li>List\n\n<ul>\n<li>Mixed list</li>\n</ul></li>\n</ol>\n",
"* Start with unordered\n 1. Ordered\n",
"<ul>\n<li>Start with unordered\n\n<ol>\n<li>Ordered</li>\n</ol></li>\n</ul>\n",
"* Start with unordered\n 1. Ordered\n",
"<ul>\n<li>Start with unordered\n\n<ol>\n<li>Ordered</li>\n</ol></li>\n</ul>\n",
"1. numbers\n1. are ignored\n",
"<ol>\n<li>numbers</li>\n<li>are ignored</li>\n</ol>\n",
Fix bug with gathering list item lines Instead of swallowing an empty line and then reintroducing it back again in certain cases, collect the list item body in an unaltered form and let the recursive parsing call sort things out. Fixes issue #228.
2015-12-27 02:18:22 +08:00
`1. Foo
bar
qux
`,
`<ol>
<li><p>Foo</p>
<pre><code>bar
qux
</code></pre></li>
</ol>
`,
horizontal rule and list testing
2011-06-28 06:06:32 +08:00
}
doTestsBlock(t, tests, 0)
}
preformatted html block tests
2011-06-28 09:35:40 +08:00
Add definition lists extension support
2015-05-29 19:30:49 +08:00
func TestDefinitionList(t *testing.T) {
var tests = []string{
"Term 1\n: Definition a\n",
"<dl>\n<dt>Term 1</dt>\n<dd>Definition a</dd>\n</dl>\n",
"Term 1\n: Definition a \n",
"<dl>\n<dt>Term 1</dt>\n<dd>Definition a</dd>\n</dl>\n",
"Term 1\n: Definition a\n: Definition b\n",
"<dl>\n<dt>Term 1</dt>\n<dd>Definition a</dd>\n<dd>Definition b</dd>\n</dl>\n",
"Term 1\n: Definition a\n\nTerm 2\n: Definition b\n",
"<dl>\n" +
"<dt>Term 1</dt>\n" +
"<dd>Definition a</dd>\n" +
"<dt>Term 2</dt>\n" +
"<dd>Definition b</dd>\n" +
"</dl>\n",
Fix definition lists end-of-list detection
2015-06-07 15:36:53 +08:00
"Term 1\n: Definition a\n\nTerm 2\n: Definition b\n\nTerm 3\n: Definition c\n",
"<dl>\n" +
"<dt>Term 1</dt>\n" +
"<dd>Definition a</dd>\n" +
"<dt>Term 2</dt>\n" +
"<dd>Definition b</dd>\n" +
"<dt>Term 3</dt>\n" +
"<dd>Definition c</dd>\n" +
"</dl>\n",
Add definition lists extension support
2015-05-29 19:30:49 +08:00
"Term 1\n: Definition a\n: Definition b\n\nTerm 2\n: Definition c\n",
"<dl>\n" +
"<dt>Term 1</dt>\n" +
"<dd>Definition a</dd>\n" +
"<dd>Definition b</dd>\n" +
"<dt>Term 2</dt>\n" +
"<dd>Definition c</dd>\n" +
"</dl>\n",
"Term 1\n\n: Definition a\n\nTerm 2\n\n: Definition b\n",
"<dl>\n" +
"<dt>Term 1</dt>\n" +
"<dd><p>Definition a</p></dd>\n" +
"<dt>Term 2</dt>\n" +
"<dd><p>Definition b</p></dd>\n" +
"</dl>\n",
"Term 1\n\n: Definition a\n\n: Definition b\n\nTerm 2\n\n: Definition c\n",
"<dl>\n" +
"<dt>Term 1</dt>\n" +
"<dd><p>Definition a</p></dd>\n" +
"<dd><p>Definition b</p></dd>\n" +
"<dt>Term 2</dt>\n" +
"<dd><p>Definition c</p></dd>\n" +
"</dl>\n",
"Term 1\n: Definition a\nNext line\n",
"<dl>\n<dt>Term 1</dt>\n<dd>Definition a\nNext line</dd>\n</dl>\n",
"Term 1\n: Definition a\n Next line\n",
"<dl>\n<dt>Term 1</dt>\n<dd>Definition a\nNext line</dd>\n</dl>\n",
"Term 1\n: Definition a \n Next line \n",
"<dl>\n<dt>Term 1</dt>\n<dd>Definition a\nNext line</dd>\n</dl>\n",
"Term 1\n: Definition a\nNext line\n\nTerm 2\n: Definition b",
"<dl>\n" +
"<dt>Term 1</dt>\n" +
"<dd>Definition a\nNext line</dd>\n" +
"<dt>Term 2</dt>\n" +
"<dd>Definition b</dd>\n" +
"</dl>\n",
"Term 1\n: Definition a\n",
"<dl>\n<dt>Term 1</dt>\n<dd>Definition a</dd>\n</dl>\n",
"Term 1\n:Definition a\n",
"<p>Term 1\n:Definition a</p>\n",
"Term 1\n\n: Definition a\n\nTerm 2\n\n: Definition b\n\nText 1",
"<dl>\n" +
"<dt>Term 1</dt>\n" +
"<dd><p>Definition a</p></dd>\n" +
"<dt>Term 2</dt>\n" +
"<dd><p>Definition b</p></dd>\n" +
"</dl>\n" +
"\n<p>Text 1</p>\n",
Fix definition lists end-of-list detection
2015-06-07 15:36:53 +08:00
"Term 1\n\n: Definition a\n\nText 1\n\nTerm 2\n\n: Definition b\n\nText 2",
"<dl>\n" +
"<dt>Term 1</dt>\n" +
"<dd><p>Definition a</p></dd>\n" +
"</dl>\n" +
"\n<p>Text 1</p>\n" +
"\n<dl>\n" +
"<dt>Term 2</dt>\n" +
"<dd><p>Definition b</p></dd>\n" +
"</dl>\n" +
"\n<p>Text 2</p>\n",
Fix definition lists that contain other lists Fixes #263
2016-05-07 02:27:55 +08:00
"Term 1\n: Definition a\n\n Text 1\n\n 1. First\n 2. Second",
"<dl>\n" +
"<dt>Term 1</dt>\n" +
"<dd><p>Definition a</p>\n\n" +
"<p>Text 1</p>\n\n" +
"<ol>\n<li>First</li>\n<li>Second</li>\n</ol></dd>\n" +
"</dl>\n",
Add definition lists extension support
2015-05-29 19:30:49 +08:00
}
doTestsBlock(t, tests, EXTENSION_DEFINITION_LISTS)
}
preformatted html block tests
2011-06-28 09:35:40 +08:00
func TestPreformattedHtml(t *testing.T) {
var tests = []string{
"<div></div>\n",
"<div></div>\n",
"<div>\n</div>\n",
"<div>\n</div>\n",
"<div>\n</div>\nParagraph\n",
"<p><div>\n</div>\nParagraph</p>\n",
"<div class=\"foo\">\n</div>\n",
"<div class=\"foo\">\n</div>\n",
"<div>\nAnything here\n</div>\n",
"<div>\nAnything here\n</div>\n",
"<div>\n Anything here\n</div>\n",
"<div>\n Anything here\n</div>\n",
"<div>\nAnything here\n </div>\n",
"<div>\nAnything here\n </div>\n",
"<div>\nThis is *not* &proceessed\n</div>\n",
"<div>\nThis is *not* &proceessed\n</div>\n",
"<faketag>\n Something\n</faketag>\n",
"<p><faketag>\n Something\n</faketag></p>\n",
"<div>\n Something here\n</divv>\n",
"<p><div>\n Something here\n</divv></p>\n",
"Paragraph\n<div>\nHere? >&<\n</div>\n",
"<p>Paragraph\n<div>\nHere? &gt;&amp;&lt;\n</div></p>\n",
"Paragraph\n\n<div>\nHow about here? >&<\n</div>\n",
"<p>Paragraph</p>\n\n<div>\nHow about here? >&<\n</div>\n",
"Paragraph\n<div>\nHere? >&<\n</div>\nAnd here?\n",
"<p>Paragraph\n<div>\nHere? &gt;&amp;&lt;\n</div>\nAnd here?</p>\n",
"Paragraph\n\n<div>\nHow about here? >&<\n</div>\nAnd here?\n",
"<p>Paragraph</p>\n\n<p><div>\nHow about here? &gt;&amp;&lt;\n</div>\nAnd here?</p>\n",
"Paragraph\n<div>\nHere? >&<\n</div>\n\nAnd here?\n",
"<p>Paragraph\n<div>\nHere? &gt;&amp;&lt;\n</div></p>\n\n<p>And here?</p>\n",
"Paragraph\n\n<div>\nHow about here? >&<\n</div>\n\nAnd here?\n",
"<p>Paragraph</p>\n\n<div>\nHow about here? >&<\n</div>\n\n<p>And here?</p>\n",
}
doTestsBlock(t, tests, 0)
}
func TestPreformattedHtmlLax(t *testing.T) {
var tests = []string{
"Paragraph\n<div>\nHere? >&<\n</div>\n",
"<p>Paragraph</p>\n\n<div>\nHere? >&<\n</div>\n",
"Paragraph\n\n<div>\nHow about here? >&<\n</div>\n",
"<p>Paragraph</p>\n\n<div>\nHow about here? >&<\n</div>\n",
"Paragraph\n<div>\nHere? >&<\n</div>\nAnd here?\n",
"<p>Paragraph</p>\n\n<div>\nHere? >&<\n</div>\n\n<p>And here?</p>\n",
"Paragraph\n\n<div>\nHow about here? >&<\n</div>\nAnd here?\n",
"<p>Paragraph</p>\n\n<div>\nHow about here? >&<\n</div>\n\n<p>And here?</p>\n",
"Paragraph\n<div>\nHere? >&<\n</div>\n\nAnd here?\n",
"<p>Paragraph</p>\n\n<div>\nHere? >&<\n</div>\n\n<p>And here?</p>\n",
"Paragraph\n\n<div>\nHow about here? >&<\n</div>\n\nAnd here?\n",
"<p>Paragraph</p>\n\n<div>\nHow about here? >&<\n</div>\n\n<p>And here?</p>\n",
}
doTestsBlock(t, tests, EXTENSION_LAX_HTML_BLOCKS)
}
fenced code: ending marker must match beginning marker, tests for fenced code blocks
2011-06-29 00:30:25 +08:00
func TestFencedCodeBlock(t *testing.T) {
var tests = []string{
"``` go\nfunc foo() bool {\n\treturn true;\n}\n```\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-go\">func foo() bool {\n\treturn true;\n}\n</code></pre>\n",
fenced code: ending marker must match beginning marker, tests for fenced code blocks
2011-06-29 00:30:25 +08:00
Accept info strings in code fences (#448) * Accept info strings in code fences According to the common mark standard, code fence info strings can be anything, not just single words. Update the tests and parser accordingly. The formatter already expected an info string with a language and HTML classes, so this does not need to change. Update the LaTeX formatter to take the first word of the info string as the language. Fixes #410 (in v1). * Don't output whole info string as code classes This follows the common mark specification. * run go fmt
2018-04-28 18:25:19 +08:00
"``` go foo bar\nfunc foo() bool {\n\treturn true;\n}\n```\n",
"<pre><code class=\"language-go\">func foo() bool {\n\treturn true;\n}\n</code></pre>\n",
fenced code: ending marker must match beginning marker, tests for fenced code blocks
2011-06-29 00:30:25 +08:00
"``` c\n/* special & char < > \" escaping */\n```\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-c\">/* special &amp; char &lt; &gt; &quot; escaping */\n</code></pre>\n",
fenced code: ending marker must match beginning marker, tests for fenced code blocks
2011-06-29 00:30:25 +08:00
"``` c\nno *inline* processing ~~of text~~\n```\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-c\">no *inline* processing ~~of text~~\n</code></pre>\n",
fenced code: ending marker must match beginning marker, tests for fenced code blocks
2011-06-29 00:30:25 +08:00
"```\nNo language\n```\n",
"<pre><code>No language\n</code></pre>\n",
"``` {ocaml}\nlanguage in braces\n```\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-ocaml\">language in braces\n</code></pre>\n",
fenced code: ending marker must match beginning marker, tests for fenced code blocks
2011-06-29 00:30:25 +08:00
"``` {ocaml} \nwith extra whitespace\n```\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-ocaml\">with extra whitespace\n</code></pre>\n",
fenced code: ending marker must match beginning marker, tests for fenced code blocks
2011-06-29 00:30:25 +08:00
"```{ ocaml }\nwith extra whitespace\n```\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-ocaml\">with extra whitespace\n</code></pre>\n",
fenced code: ending marker must match beginning marker, tests for fenced code blocks
2011-06-29 00:30:25 +08:00
"~ ~~ java\nWith whitespace\n~~~\n",
"<p>~ ~~ java\nWith whitespace\n~~~</p>\n",
"~~\nonly two\n~~\n",
"<p>~~\nonly two\n~~</p>\n",
"```` python\nextra\n````\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-python\">extra\n</code></pre>\n",
fenced code: ending marker must match beginning marker, tests for fenced code blocks
2011-06-29 00:30:25 +08:00
"~~~ perl\nthree to start, four to end\n~~~~\n",
"<p>~~~ perl\nthree to start, four to end\n~~~~</p>\n",
"~~~~ perl\nfour to start, three to end\n~~~\n",
"<p>~~~~ perl\nfour to start, three to end\n~~~</p>\n",
"~~~ bash\ntildes\n~~~\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-bash\">tildes\n</code></pre>\n",
fenced code: ending marker must match beginning marker, tests for fenced code blocks
2011-06-29 00:30:25 +08:00
"``` lisp\nno ending\n",
"<p>``` lisp\nno ending</p>\n",
"~~~ lisp\nend with language\n~~~ lisp\n",
"<p>~~~ lisp\nend with language\n~~~ lisp</p>\n",
"```\nmismatched begin and end\n~~~\n",
"<p>```\nmismatched begin and end\n~~~</p>\n",
"~~~\nmismatched begin and end\n```\n",
"<p>~~~\nmismatched begin and end\n```</p>\n",
" ``` oz\nleading spaces\n```\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-oz\">leading spaces\n</code></pre>\n",
fenced code: ending marker must match beginning marker, tests for fenced code blocks
2011-06-29 00:30:25 +08:00
" ``` oz\nleading spaces\n ```\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-oz\">leading spaces\n</code></pre>\n",
fenced code: ending marker must match beginning marker, tests for fenced code blocks
2011-06-29 00:30:25 +08:00
" ``` oz\nleading spaces\n ```\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-oz\">leading spaces\n</code></pre>\n",
fenced code: ending marker must match beginning marker, tests for fenced code blocks
2011-06-29 00:30:25 +08:00
"``` oz\nleading spaces\n ```\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-oz\">leading spaces\n</code></pre>\n",
fenced code: ending marker must match beginning marker, tests for fenced code blocks
2011-06-29 00:30:25 +08:00
" ``` oz\nleading spaces\n ```\n",
"<pre><code>``` oz\n</code></pre>\n\n<p>leading spaces\n ```</p>\n",
add test cases for issue #45
2014-03-31 04:00:26 +08:00
"Bla bla\n\n``` oz\ncode blocks breakup paragraphs\n```\n\nBla Bla\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<p>Bla bla</p>\n\n<pre><code class=\"language-oz\">code blocks breakup paragraphs\n</code></pre>\n\n<p>Bla Bla</p>\n",
add test cases for issue #45
2014-03-31 04:00:26 +08:00
"Some text before a fenced code block\n``` oz\ncode blocks breakup paragraphs\n```\nAnd some text after a fenced code block",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<p>Some text before a fenced code block</p>\n\n<pre><code class=\"language-oz\">code blocks breakup paragraphs\n</code></pre>\n\n<p>And some text after a fenced code block</p>\n",
add test cases for issue #45
2014-03-31 04:00:26 +08:00
"`",
"<p>`</p>\n",
Add failing test for an issue introduced by PR #56. The issue is that when there are more than 1 fenced code blocks with a blank line before and after, the parser introduces a single extra new line to all the fenced code blocks except the last one.
2014-04-12 10:54:55 +08:00
"Bla bla\n\n``` oz\ncode blocks breakup paragraphs\n```\n\nBla Bla\n\n``` oz\nmultiple code blocks work okay\n```\n\nBla Bla\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<p>Bla bla</p>\n\n<pre><code class=\"language-oz\">code blocks breakup paragraphs\n</code></pre>\n\n<p>Bla Bla</p>\n\n<pre><code class=\"language-oz\">multiple code blocks work okay\n</code></pre>\n\n<p>Bla Bla</p>\n",
Add failing test for an issue introduced by PR #56. The issue is that when there are more than 1 fenced code blocks with a blank line before and after, the parser introduces a single extra new line to all the fenced code blocks except the last one.
2014-04-12 10:54:55 +08:00
"Some text before a fenced code block\n``` oz\ncode blocks breakup paragraphs\n```\nSome text in between\n``` oz\nmultiple code blocks work okay\n```\nAnd some text after a fenced code block",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<p>Some text before a fenced code block</p>\n\n<pre><code class=\"language-oz\">code blocks breakup paragraphs\n</code></pre>\n\n<p>Some text in between</p>\n\n<pre><code class=\"language-oz\">multiple code blocks work okay\n</code></pre>\n\n<p>And some text after a fenced code block</p>\n",
Improve fenced code block detection for first pass. In first pass, there may not be a trailing newline after a fenced code block yet. Make newline optional in isFenceLine when calling fencedCodeBlock to detect the fenced code block it anyway. This is more complex, but it avoids creating temporary buffers or modifying input in order to maintain performance (see #148). Document and rename fencedCode to fencedCodeBlock. Add regression tests. Fixes #279.
2016-07-16 02:51:15 +08:00
"```\n[]:()\n```\n",
"<pre><code>[]:()\n</code></pre>\n",
"```\n[]:()\n[]:)\n[]:(\n[]:x\n[]:testing\n[:testing\n\n[]:\nlinebreak\n[]()\n\n[]:\n[]()\n```",
"<pre><code>[]:()\n[]:)\n[]:(\n[]:x\n[]:testing\n[:testing\n\n[]:\nlinebreak\n[]()\n\n[]:\n[]()\n</code></pre>\n",
fenced code: ending marker must match beginning marker, tests for fenced code blocks
2011-06-29 00:30:25 +08:00
}
doTestsBlock(t, tests, EXTENSION_FENCED_CODE)
}
table unit tests and fix for a crash uncovered by them
2011-07-26 01:39:02 +08:00
Fix fenced code processing inside blockquotes Add a call to fenced code block processor inside the loop that's responsible for collecting the quoted lines. Grok all the fenced code block as a part of the quoted text. Closes #122.
2015-10-30 02:06:27 +08:00
func TestFencedCodeInsideBlockquotes(t *testing.T) {
Make test values more readable, add additional test cases.
2015-11-01 05:35:21 +08:00
cat := func(s ...string) string { return strings.Join(s, "\n") }
Fix fenced code processing inside blockquotes Add a call to fenced code block processor inside the loop that's responsible for collecting the quoted lines. Grok all the fenced code block as a part of the quoted text. Closes #122.
2015-10-30 02:06:27 +08:00
var tests = []string{
Make test values more readable, add additional test cases.
2015-11-01 05:35:21 +08:00
cat("> ```go",
"package moo",
"",
"```",
""),
Fix fenced code processing inside blockquotes Add a call to fenced code block processor inside the loop that's responsible for collecting the quoted lines. Grok all the fenced code block as a part of the quoted text. Closes #122.
2015-10-30 02:06:27 +08:00
`<blockquote>
<pre><code class="language-go">package moo
</code></pre>
</blockquote>
`,
// -------------------------------------------
Make test values more readable, add additional test cases.
2015-11-01 05:35:21 +08:00
cat("> foo",
"> ",
"> ```go",
"package moo",
"```",
"> ",
"> goo.",
""),
Fix fenced code processing inside blockquotes Add a call to fenced code block processor inside the loop that's responsible for collecting the quoted lines. Grok all the fenced code block as a part of the quoted text. Closes #122.
2015-10-30 02:06:27 +08:00
`<blockquote>
<p>foo</p>
<pre><code class="language-go">package moo
</code></pre>
<p>goo.</p>
</blockquote>
`,
// -------------------------------------------
Make test values more readable, add additional test cases.
2015-11-01 05:35:21 +08:00
cat("> foo",
"> ",
"> quote",
"continues",
"```",
""),
`<blockquote>
<p>foo</p>
<p>quote
continues
` + "```" + `</p>
</blockquote>
`,
// -------------------------------------------
cat("> foo",
"> ",
"> ```go",
"package moo",
"```",
"> ",
"> goo.",
"> ",
"> ```go",
"package zoo",
"```",
"> ",
"> woo.",
""),
Fix fenced code processing inside blockquotes Add a call to fenced code block processor inside the loop that's responsible for collecting the quoted lines. Grok all the fenced code block as a part of the quoted text. Closes #122.
2015-10-30 02:06:27 +08:00
`<blockquote>
<p>foo</p>
<pre><code class="language-go">package moo
</code></pre>
<p>goo.</p>
<pre><code class="language-go">package zoo
</code></pre>
<p>woo.</p>
</blockquote>
`,
}
Make test values more readable, add additional test cases.
2015-11-01 05:35:21 +08:00
// These 2 alternative forms of blockquoted fenced code blocks should produce same output.
forms := [2]string{
cat("> plain quoted text",
"> ```fenced",
"code",
" with leading single space correctly preserved",
"okay",
"```",
"> rest of quoted text"),
cat("> plain quoted text",
"> ```fenced",
"> code",
"> with leading single space correctly preserved",
"> okay",
"> ```",
"> rest of quoted text"),
}
want := `<blockquote>
<p>plain quoted text</p>
<pre><code class="language-fenced">code
with leading single space correctly preserved
okay
</code></pre>
<p>rest of quoted text</p>
</blockquote>
`
tests = append(tests, forms[0], want)
tests = append(tests, forms[1], want)
Fix fenced code processing inside blockquotes Add a call to fenced code block processor inside the loop that's responsible for collecting the quoted lines. Grok all the fenced code block as a part of the quoted text. Closes #122.
2015-10-30 02:06:27 +08:00
doTestsBlock(t, tests, EXTENSION_FENCED_CODE)
}
table unit tests and fix for a crash uncovered by them
2011-07-26 01:39:02 +08:00
func TestTable(t *testing.T) {
var tests = []string{
"a | b\n---|---\nc | d\n",
Updated tests to check for th tags instead of td tags within thead blocks
2013-10-17 17:35:44 +08:00
"<table>\n<thead>\n<tr>\n<th>a</th>\n<th>b</th>\n</tr>\n</thead>\n\n" +
table unit tests and fix for a crash uncovered by them
2011-07-26 01:39:02 +08:00
"<tbody>\n<tr>\n<td>c</td>\n<td>d</td>\n</tr>\n</tbody>\n</table>\n",
"a | b\n---|--\nc | d\n",
"<p>a | b\n---|--\nc | d</p>\n",
"|a|b|c|d|\n|----|----|----|---|\n|e|f|g|h|\n",
Updated tests to check for th tags instead of td tags within thead blocks
2013-10-17 17:35:44 +08:00
"<table>\n<thead>\n<tr>\n<th>a</th>\n<th>b</th>\n<th>c</th>\n<th>d</th>\n</tr>\n</thead>\n\n" +
table unit tests and fix for a crash uncovered by them
2011-07-26 01:39:02 +08:00
"<tbody>\n<tr>\n<td>e</td>\n<td>f</td>\n<td>g</td>\n<td>h</td>\n</tr>\n</tbody>\n</table>\n",
"*a*|__b__|[c](C)|d\n---|---|---|---\ne|f|g|h\n",
Updated tests to check for th tags instead of td tags within thead blocks
2013-10-17 17:35:44 +08:00
"<table>\n<thead>\n<tr>\n<th><em>a</em></th>\n<th><strong>b</strong></th>\n<th><a href=\"C\">c</a></th>\n<th>d</th>\n</tr>\n</thead>\n\n" +
table unit tests and fix for a crash uncovered by them
2011-07-26 01:39:02 +08:00
"<tbody>\n<tr>\n<td>e</td>\n<td>f</td>\n<td>g</td>\n<td>h</td>\n</tr>\n</tbody>\n</table>\n",
"a|b|c\n---|---|---\nd|e|f\ng|h\ni|j|k|l|m\nn|o|p\n",
Updated tests to check for th tags instead of td tags within thead blocks
2013-10-17 17:35:44 +08:00
"<table>\n<thead>\n<tr>\n<th>a</th>\n<th>b</th>\n<th>c</th>\n</tr>\n</thead>\n\n" +
table unit tests and fix for a crash uncovered by them
2011-07-26 01:39:02 +08:00
"<tbody>\n<tr>\n<td>d</td>\n<td>e</td>\n<td>f</td>\n</tr>\n\n" +
"<tr>\n<td>g</td>\n<td>h</td>\n<td></td>\n</tr>\n\n" +
"<tr>\n<td>i</td>\n<td>j</td>\n<td>k</td>\n</tr>\n\n" +
"<tr>\n<td>n</td>\n<td>o</td>\n<td>p</td>\n</tr>\n</tbody>\n</table>\n",
"a|b|c\n---|---|---\n*d*|__e__|f\n",
Updated tests to check for th tags instead of td tags within thead blocks
2013-10-17 17:35:44 +08:00
"<table>\n<thead>\n<tr>\n<th>a</th>\n<th>b</th>\n<th>c</th>\n</tr>\n</thead>\n\n" +
table unit tests and fix for a crash uncovered by them
2011-07-26 01:39:02 +08:00
"<tbody>\n<tr>\n<td><em>d</em></td>\n<td><strong>e</strong></td>\n<td>f</td>\n</tr>\n</tbody>\n</table>\n",
"a|b|c|d\n:--|--:|:-:|---\ne|f|g|h\n",
Updated tests to check for th tags instead of td tags within thead blocks
2013-10-17 17:35:44 +08:00
"<table>\n<thead>\n<tr>\n<th align=\"left\">a</th>\n<th align=\"right\">b</th>\n" +
"<th align=\"center\">c</th>\n<th>d</th>\n</tr>\n</thead>\n\n" +
table unit tests and fix for a crash uncovered by them
2011-07-26 01:39:02 +08:00
"<tbody>\n<tr>\n<td align=\"left\">e</td>\n<td align=\"right\">f</td>\n" +
"<td align=\"center\">g</td>\n<td>h</td>\n</tr>\n</tbody>\n</table>\n",
"a|b|c\n---|---|---\n",
Updated tests to check for th tags instead of td tags within thead blocks
2013-10-17 17:35:44 +08:00
"<table>\n<thead>\n<tr>\n<th>a</th>\n<th>b</th>\n<th>c</th>\n</tr>\n</thead>\n\n<tbody>\n</tbody>\n</table>\n",
table unit tests and fix for a crash uncovered by them
2011-07-26 01:39:02 +08:00
"a| b|c | d | e\n---|---|---|---|---\nf| g|h | i |j\n",
Updated tests to check for th tags instead of td tags within thead blocks
2013-10-17 17:35:44 +08:00
"<table>\n<thead>\n<tr>\n<th>a</th>\n<th>b</th>\n<th>c</th>\n<th>d</th>\n<th>e</th>\n</tr>\n</thead>\n\n" +
table unit tests and fix for a crash uncovered by them
2011-07-26 01:39:02 +08:00
"<tbody>\n<tr>\n<td>f</td>\n<td>g</td>\n<td>h</td>\n<td>i</td>\n<td>j</td>\n</tr>\n</tbody>\n</table>\n",
permit backslash-escaped vertical bars in tables
2011-09-14 06:23:24 +08:00
"a|b\\|c|d\n---|---|---\nf|g\\|h|i\n",
Updated tests to check for th tags instead of td tags within thead blocks
2013-10-17 17:35:44 +08:00
"<table>\n<thead>\n<tr>\n<th>a</th>\n<th>b|c</th>\n<th>d</th>\n</tr>\n</thead>\n\n<tbody>\n<tr>\n<td>f</td>\n<td>g|h</td>\n<td>i</td>\n</tr>\n</tbody>\n</table>\n",
table unit tests and fix for a crash uncovered by them
2011-07-26 01:39:02 +08:00
}
doTestsBlock(t, tests, EXTENSION_TABLES)
}
add EXTENSION_NO_EMPTY_LINE_BEFORE_BLOCK flag to make it closer to GFM(Github flavor Markdown)
2013-07-30 10:32:11 +08:00
func TestUnorderedListWith_EXTENSION_NO_EMPTY_LINE_BEFORE_BLOCK(t *testing.T) {
var tests = []string{
"* Hello\n",
"<ul>\n<li>Hello</li>\n</ul>\n",
"* Yin\n* Yang\n",
"<ul>\n<li>Yin</li>\n<li>Yang</li>\n</ul>\n",
"* Ting\n* Bong\n* Goo\n",
"<ul>\n<li>Ting</li>\n<li>Bong</li>\n<li>Goo</li>\n</ul>\n",
"* Yin\n\n* Yang\n",
"<ul>\n<li><p>Yin</p></li>\n\n<li><p>Yang</p></li>\n</ul>\n",
"* Ting\n\n* Bong\n* Goo\n",
"<ul>\n<li><p>Ting</p></li>\n\n<li><p>Bong</p></li>\n\n<li><p>Goo</p></li>\n</ul>\n",
"+ Hello\n",
"<ul>\n<li>Hello</li>\n</ul>\n",
"+ Yin\n+ Yang\n",
"<ul>\n<li>Yin</li>\n<li>Yang</li>\n</ul>\n",
"+ Ting\n+ Bong\n+ Goo\n",
"<ul>\n<li>Ting</li>\n<li>Bong</li>\n<li>Goo</li>\n</ul>\n",
"+ Yin\n\n+ Yang\n",
"<ul>\n<li><p>Yin</p></li>\n\n<li><p>Yang</p></li>\n</ul>\n",
"+ Ting\n\n+ Bong\n+ Goo\n",
"<ul>\n<li><p>Ting</p></li>\n\n<li><p>Bong</p></li>\n\n<li><p>Goo</p></li>\n</ul>\n",
"- Hello\n",
"<ul>\n<li>Hello</li>\n</ul>\n",
"- Yin\n- Yang\n",
"<ul>\n<li>Yin</li>\n<li>Yang</li>\n</ul>\n",
"- Ting\n- Bong\n- Goo\n",
"<ul>\n<li>Ting</li>\n<li>Bong</li>\n<li>Goo</li>\n</ul>\n",
"- Yin\n\n- Yang\n",
"<ul>\n<li><p>Yin</p></li>\n\n<li><p>Yang</p></li>\n</ul>\n",
"- Ting\n\n- Bong\n- Goo\n",
"<ul>\n<li><p>Ting</p></li>\n\n<li><p>Bong</p></li>\n\n<li><p>Goo</p></li>\n</ul>\n",
"*Hello\n",
"<p>*Hello</p>\n",
"* Hello \n",
"<ul>\n<li>Hello</li>\n</ul>\n",
"* Hello \n Next line \n",
"<ul>\n<li>Hello\nNext line</li>\n</ul>\n",
"Paragraph\n* No linebreak\n",
"<p>Paragraph</p>\n\n<ul>\n<li>No linebreak</li>\n</ul>\n",
"Paragraph\n\n* Linebreak\n",
"<p>Paragraph</p>\n\n<ul>\n<li>Linebreak</li>\n</ul>\n",
"* List\n * Nested list\n",
"<ul>\n<li>List\n\n<ul>\n<li>Nested list</li>\n</ul></li>\n</ul>\n",
"* List\n\n * Nested list\n",
"<ul>\n<li><p>List</p>\n\n<ul>\n<li>Nested list</li>\n</ul></li>\n</ul>\n",
"* List\n Second line\n\n + Nested\n",
"<ul>\n<li><p>List\nSecond line</p>\n\n<ul>\n<li>Nested</li>\n</ul></li>\n</ul>\n",
"* List\n + Nested\n\n Continued\n",
"<ul>\n<li><p>List</p>\n\n<ul>\n<li>Nested</li>\n</ul>\n\n<p>Continued</p></li>\n</ul>\n",
"* List\n * shallow indent\n",
"<ul>\n<li>List\n\n<ul>\n<li>shallow indent</li>\n</ul></li>\n</ul>\n",
"* List\n" +
" * shallow indent\n" +
" * part of second list\n" +
" * still second\n" +
" * almost there\n" +
" * third level\n",
"<ul>\n" +
"<li>List\n\n" +
"<ul>\n" +
"<li>shallow indent</li>\n" +
"<li>part of second list</li>\n" +
"<li>still second</li>\n" +
"<li>almost there\n\n" +
"<ul>\n" +
"<li>third level</li>\n" +
"</ul></li>\n" +
"</ul></li>\n" +
"</ul>\n",
"* List\n extra indent, same paragraph\n",
"<ul>\n<li>List\n extra indent, same paragraph</li>\n</ul>\n",
"* List\n\n code block\n",
"<ul>\n<li><p>List</p>\n\n<pre><code>code block\n</code></pre></li>\n</ul>\n",
"* List\n\n code block with spaces\n",
"<ul>\n<li><p>List</p>\n\n<pre><code> code block with spaces\n</code></pre></li>\n</ul>\n",
"* List\n\n * sublist\n\n normal text\n\n * another sublist\n",
"<ul>\n<li><p>List</p>\n\n<ul>\n<li>sublist</li>\n</ul>\n\n<p>normal text</p>\n\n<ul>\n<li>another sublist</li>\n</ul></li>\n</ul>\n",
}
doTestsBlock(t, tests, EXTENSION_NO_EMPTY_LINE_BEFORE_BLOCK)
}
func TestOrderedList_EXTENSION_NO_EMPTY_LINE_BEFORE_BLOCK(t *testing.T) {
var tests = []string{
"1. Hello\n",
"<ol>\n<li>Hello</li>\n</ol>\n",
"1. Yin\n2. Yang\n",
"<ol>\n<li>Yin</li>\n<li>Yang</li>\n</ol>\n",
"1. Ting\n2. Bong\n3. Goo\n",
"<ol>\n<li>Ting</li>\n<li>Bong</li>\n<li>Goo</li>\n</ol>\n",
"1. Yin\n\n2. Yang\n",
"<ol>\n<li><p>Yin</p></li>\n\n<li><p>Yang</p></li>\n</ol>\n",
"1. Ting\n\n2. Bong\n3. Goo\n",
"<ol>\n<li><p>Ting</p></li>\n\n<li><p>Bong</p></li>\n\n<li><p>Goo</p></li>\n</ol>\n",
"1 Hello\n",
"<p>1 Hello</p>\n",
"1.Hello\n",
"<p>1.Hello</p>\n",
"1. Hello \n",
"<ol>\n<li>Hello</li>\n</ol>\n",
"1. Hello \n Next line \n",
"<ol>\n<li>Hello\nNext line</li>\n</ol>\n",
"Paragraph\n1. No linebreak\n",
"<p>Paragraph</p>\n\n<ol>\n<li>No linebreak</li>\n</ol>\n",
"Paragraph\n\n1. Linebreak\n",
"<p>Paragraph</p>\n\n<ol>\n<li>Linebreak</li>\n</ol>\n",
"1. List\n 1. Nested list\n",
"<ol>\n<li>List\n\n<ol>\n<li>Nested list</li>\n</ol></li>\n</ol>\n",
"1. List\n\n 1. Nested list\n",
"<ol>\n<li><p>List</p>\n\n<ol>\n<li>Nested list</li>\n</ol></li>\n</ol>\n",
"1. List\n Second line\n\n 1. Nested\n",
"<ol>\n<li><p>List\nSecond line</p>\n\n<ol>\n<li>Nested</li>\n</ol></li>\n</ol>\n",
"1. List\n 1. Nested\n\n Continued\n",
"<ol>\n<li><p>List</p>\n\n<ol>\n<li>Nested</li>\n</ol>\n\n<p>Continued</p></li>\n</ol>\n",
"1. List\n 1. shallow indent\n",
"<ol>\n<li>List\n\n<ol>\n<li>shallow indent</li>\n</ol></li>\n</ol>\n",
"1. List\n" +
" 1. shallow indent\n" +
" 2. part of second list\n" +
" 3. still second\n" +
" 4. almost there\n" +
" 1. third level\n",
"<ol>\n" +
"<li>List\n\n" +
"<ol>\n" +
"<li>shallow indent</li>\n" +
"<li>part of second list</li>\n" +
"<li>still second</li>\n" +
"<li>almost there\n\n" +
"<ol>\n" +
"<li>third level</li>\n" +
"</ol></li>\n" +
"</ol></li>\n" +
"</ol>\n",
"1. List\n extra indent, same paragraph\n",
"<ol>\n<li>List\n extra indent, same paragraph</li>\n</ol>\n",
"1. List\n\n code block\n",
"<ol>\n<li><p>List</p>\n\n<pre><code>code block\n</code></pre></li>\n</ol>\n",
"1. List\n\n code block with spaces\n",
"<ol>\n<li><p>List</p>\n\n<pre><code> code block with spaces\n</code></pre></li>\n</ol>\n",
"1. List\n * Mixted list\n",
"<ol>\n<li>List\n\n<ul>\n<li>Mixted list</li>\n</ul></li>\n</ol>\n",
"1. List\n * Mixed list\n",
"<ol>\n<li>List\n\n<ul>\n<li>Mixed list</li>\n</ul></li>\n</ol>\n",
"* Start with unordered\n 1. Ordered\n",
"<ul>\n<li>Start with unordered\n\n<ol>\n<li>Ordered</li>\n</ol></li>\n</ul>\n",
"* Start with unordered\n 1. Ordered\n",
"<ul>\n<li>Start with unordered\n\n<ol>\n<li>Ordered</li>\n</ol></li>\n</ul>\n",
"1. numbers\n1. are ignored\n",
"<ol>\n<li>numbers</li>\n<li>are ignored</li>\n</ol>\n",
}
doTestsBlock(t, tests, EXTENSION_NO_EMPTY_LINE_BEFORE_BLOCK)
}
func TestFencedCodeBlock_EXTENSION_NO_EMPTY_LINE_BEFORE_BLOCK(t *testing.T) {
var tests = []string{
"``` go\nfunc foo() bool {\n\treturn true;\n}\n```\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-go\">func foo() bool {\n\treturn true;\n}\n</code></pre>\n",
add EXTENSION_NO_EMPTY_LINE_BEFORE_BLOCK flag to make it closer to GFM(Github flavor Markdown)
2013-07-30 10:32:11 +08:00
Accept info strings in code fences (#448) * Accept info strings in code fences According to the common mark standard, code fence info strings can be anything, not just single words. Update the tests and parser accordingly. The formatter already expected an info string with a language and HTML classes, so this does not need to change. Update the LaTeX formatter to take the first word of the info string as the language. Fixes #410 (in v1). * Don't output whole info string as code classes This follows the common mark specification. * run go fmt
2018-04-28 18:25:19 +08:00
"``` go foo bar\nfunc foo() bool {\n\treturn true;\n}\n```\n",
"<pre><code class=\"language-go\">func foo() bool {\n\treturn true;\n}\n</code></pre>\n",
add EXTENSION_NO_EMPTY_LINE_BEFORE_BLOCK flag to make it closer to GFM(Github flavor Markdown)
2013-07-30 10:32:11 +08:00
"``` c\n/* special & char < > \" escaping */\n```\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-c\">/* special &amp; char &lt; &gt; &quot; escaping */\n</code></pre>\n",
add EXTENSION_NO_EMPTY_LINE_BEFORE_BLOCK flag to make it closer to GFM(Github flavor Markdown)
2013-07-30 10:32:11 +08:00
"``` c\nno *inline* processing ~~of text~~\n```\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-c\">no *inline* processing ~~of text~~\n</code></pre>\n",
add EXTENSION_NO_EMPTY_LINE_BEFORE_BLOCK flag to make it closer to GFM(Github flavor Markdown)
2013-07-30 10:32:11 +08:00
"```\nNo language\n```\n",
"<pre><code>No language\n</code></pre>\n",
"``` {ocaml}\nlanguage in braces\n```\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-ocaml\">language in braces\n</code></pre>\n",
add EXTENSION_NO_EMPTY_LINE_BEFORE_BLOCK flag to make it closer to GFM(Github flavor Markdown)
2013-07-30 10:32:11 +08:00
"``` {ocaml} \nwith extra whitespace\n```\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-ocaml\">with extra whitespace\n</code></pre>\n",
add EXTENSION_NO_EMPTY_LINE_BEFORE_BLOCK flag to make it closer to GFM(Github flavor Markdown)
2013-07-30 10:32:11 +08:00
"```{ ocaml }\nwith extra whitespace\n```\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-ocaml\">with extra whitespace\n</code></pre>\n",
add EXTENSION_NO_EMPTY_LINE_BEFORE_BLOCK flag to make it closer to GFM(Github flavor Markdown)
2013-07-30 10:32:11 +08:00
"~ ~~ java\nWith whitespace\n~~~\n",
"<p>~ ~~ java\nWith whitespace\n~~~</p>\n",
"~~\nonly two\n~~\n",
"<p>~~\nonly two\n~~</p>\n",
"```` python\nextra\n````\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-python\">extra\n</code></pre>\n",
add EXTENSION_NO_EMPTY_LINE_BEFORE_BLOCK flag to make it closer to GFM(Github flavor Markdown)
2013-07-30 10:32:11 +08:00
"~~~ perl\nthree to start, four to end\n~~~~\n",
"<p>~~~ perl\nthree to start, four to end\n~~~~</p>\n",
"~~~~ perl\nfour to start, three to end\n~~~\n",
"<p>~~~~ perl\nfour to start, three to end\n~~~</p>\n",
"~~~ bash\ntildes\n~~~\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-bash\">tildes\n</code></pre>\n",
add EXTENSION_NO_EMPTY_LINE_BEFORE_BLOCK flag to make it closer to GFM(Github flavor Markdown)
2013-07-30 10:32:11 +08:00
"``` lisp\nno ending\n",
"<p>``` lisp\nno ending</p>\n",
"~~~ lisp\nend with language\n~~~ lisp\n",
"<p>~~~ lisp\nend with language\n~~~ lisp</p>\n",
"```\nmismatched begin and end\n~~~\n",
"<p>```\nmismatched begin and end\n~~~</p>\n",
"~~~\nmismatched begin and end\n```\n",
"<p>~~~\nmismatched begin and end\n```</p>\n",
" ``` oz\nleading spaces\n```\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-oz\">leading spaces\n</code></pre>\n",
add EXTENSION_NO_EMPTY_LINE_BEFORE_BLOCK flag to make it closer to GFM(Github flavor Markdown)
2013-07-30 10:32:11 +08:00
" ``` oz\nleading spaces\n ```\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-oz\">leading spaces\n</code></pre>\n",
add EXTENSION_NO_EMPTY_LINE_BEFORE_BLOCK flag to make it closer to GFM(Github flavor Markdown)
2013-07-30 10:32:11 +08:00
" ``` oz\nleading spaces\n ```\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-oz\">leading spaces\n</code></pre>\n",
add EXTENSION_NO_EMPTY_LINE_BEFORE_BLOCK flag to make it closer to GFM(Github flavor Markdown)
2013-07-30 10:32:11 +08:00
"``` oz\nleading spaces\n ```\n",
Fixup tests after 67002b0
2014-08-29 20:26:37 +08:00
"<pre><code class=\"language-oz\">leading spaces\n</code></pre>\n",
add EXTENSION_NO_EMPTY_LINE_BEFORE_BLOCK flag to make it closer to GFM(Github flavor Markdown)
2013-07-30 10:32:11 +08:00
" ``` oz\nleading spaces\n ```\n",
"<pre><code>``` oz\n</code></pre>\n\n<p>leading spaces</p>\n\n<pre><code>```\n</code></pre>\n",
}
doTestsBlock(t, tests, EXTENSION_FENCED_CODE|EXTENSION_NO_EMPTY_LINE_BEFORE_BLOCK)
}
Add titleblock support
2014-08-02 10:54:21 +08:00
func TestTitleBlock_EXTENSION_TITLEBLOCK(t *testing.T) {
var tests = []string{
"% Some title\n" +
"% Another title line\n" +
"% Yep, more here too\n",
"<h1 class=\"title\">" +
"Some title\n" +
"Another title line\n" +
"Yep, more here too\n" +
"</h1>",
}
doTestsBlock(t, tests, EXTENSION_TITLEBLOCK)
Handle comments within a block Added test cases both for inline and block workflows. Closes #136.
2015-10-11 16:01:48 +08:00
}
Add titleblock support
2014-08-02 10:54:21 +08:00
Handle comments within a block Added test cases both for inline and block workflows. Closes #136.
2015-10-11 16:01:48 +08:00
func TestBlockComments(t *testing.T) {
var tests = []string{
"Some text\n\n<!-- comment -->\n",
"<p>Some text</p>\n\n<!-- comment -->\n",
Spread out test cases for readability
2015-10-21 01:31:08 +08:00
Handle comments within a block Added test cases both for inline and block workflows. Closes #136.
2015-10-11 16:01:48 +08:00
"Some text\n\n<!--\n\nmultiline\ncomment\n-->\n",
"<p>Some text</p>\n\n<!--\n\nmultiline\ncomment\n-->\n",
Spread out test cases for readability
2015-10-21 01:31:08 +08:00
Handle comments within a block Added test cases both for inline and block workflows. Closes #136.
2015-10-11 16:01:48 +08:00
"Some text\n\n<!--\n\n<div><p>Commented</p>\n<span>html</span></div>\n-->\n",
"<p>Some text</p>\n\n<!--\n\n<div><p>Commented</p>\n<span>html</span></div>\n-->\n",
}
doTestsBlock(t, tests, 0)
Add titleblock support
2014-08-02 10:54:21 +08:00
}
Implement support for CDATA section Fixes #165.
2015-12-15 02:23:49 +08:00
func TestCDATA(t *testing.T) {
var tests = []string{
"Some text\n\n<![CDATA[foo]]>\n",
"<p>Some text</p>\n\n<![CDATA[foo]]>\n",
"CDATA ]]\n\n<![CDATA[]]]]>\n",
"<p>CDATA ]]</p>\n\n<![CDATA[]]]]>\n",
"CDATA >\n\n<![CDATA[>]]>\n",
"<p>CDATA &gt;</p>\n\n<![CDATA[>]]>\n",
"Lots of text\n\n<![CDATA[lots of te><t\non\nseveral\nlines]]>\n",
"<p>Lots of text</p>\n\n<![CDATA[lots of te><t\non\nseveral\nlines]]>\n",
Add a few more CDATA tests
2015-12-17 02:53:40 +08:00
"<![CDATA[>]]>\n",
"<![CDATA[>]]>\n",
Implement support for CDATA section Fixes #165.
2015-12-15 02:23:49 +08:00
}
doTestsBlock(t, tests, 0)
Add a few more CDATA tests
2015-12-17 02:53:40 +08:00
doTestsBlock(t, []string{
"``` html\n<![CDATA[foo]]>\n```\n",
"<pre><code class=\"language-html\">&lt;![CDATA[foo]]&gt;\n</code></pre>\n",
"<![CDATA[\n``` python\ndef func():\n pass\n```\n]]>\n",
"<![CDATA[\n``` python\ndef func():\n pass\n```\n]]>\n",
`<![CDATA[
> def func():
> pass
]]>
`,
`<![CDATA[
> def func():
> pass
]]>
`,
}, EXTENSION_FENCED_CODE)
Implement support for CDATA section Fixes #165.
2015-12-15 02:23:49 +08:00
}
Improve fence line detection. Rename isFenceCode to isFenceLine, document it, add tests. Add support for making newline optional, this will be needed in future commits.
2016-07-16 02:41:27 +08:00
func TestIsFenceLine(t *testing.T) {
tests := []struct {
data []byte
Accept info strings in code fences (#448) * Accept info strings in code fences According to the common mark standard, code fence info strings can be anything, not just single words. Update the tests and parser accordingly. The formatter already expected an info string with a language and HTML classes, so this does not need to change. Update the LaTeX formatter to take the first word of the info string as the language. Fixes #410 (in v1). * Don't output whole info string as code classes This follows the common mark specification. * run go fmt
2018-04-28 18:25:19 +08:00
infoRequested bool
Improve fence line detection. Rename isFenceCode to isFenceLine, document it, add tests. Add support for making newline optional, this will be needed in future commits.
2016-07-16 02:41:27 +08:00
newlineOptional bool
wantEnd int
wantMarker string
Accept info strings in code fences (#448) * Accept info strings in code fences According to the common mark standard, code fence info strings can be anything, not just single words. Update the tests and parser accordingly. The formatter already expected an info string with a language and HTML classes, so this does not need to change. Update the LaTeX formatter to take the first word of the info string as the language. Fixes #410 (in v1). * Don't output whole info string as code classes This follows the common mark specification. * run go fmt
2018-04-28 18:25:19 +08:00
wantInfo string
Improve fence line detection. Rename isFenceCode to isFenceLine, document it, add tests. Add support for making newline optional, this will be needed in future commits.
2016-07-16 02:41:27 +08:00
}{
{
data: []byte("```"),
wantEnd: 0,
},
{
data: []byte("```\nstuff here\n"),
wantEnd: 4,
wantMarker: "```",
},
Make newline mandatory for opening fence line. (#281) This was an unintended typo/mistake in #280. This is stricter, and it's fine. The opening fence line will always need to have a newline. Add another test for isFenceLine.
2016-07-16 23:34:03 +08:00
{
Accept info strings in code fences (#448) * Accept info strings in code fences According to the common mark standard, code fence info strings can be anything, not just single words. Update the tests and parser accordingly. The formatter already expected an info string with a language and HTML classes, so this does not need to change. Update the LaTeX formatter to take the first word of the info string as the language. Fixes #410 (in v1). * Don't output whole info string as code classes This follows the common mark specification. * run go fmt
2018-04-28 18:25:19 +08:00
data: []byte("```\nstuff here\n"),
infoRequested: true,
wantEnd: 4,
wantMarker: "```",
Make newline mandatory for opening fence line. (#281) This was an unintended typo/mistake in #280. This is stricter, and it's fine. The opening fence line will always need to have a newline. Add another test for isFenceLine.
2016-07-16 23:34:03 +08:00
},
Improve fence line detection. Rename isFenceCode to isFenceLine, document it, add tests. Add support for making newline optional, this will be needed in future commits.
2016-07-16 02:41:27 +08:00
{
data: []byte("stuff here\n```\n"),
wantEnd: 0,
},
{
data: []byte("```"),
newlineOptional: true,
wantEnd: 3,
wantMarker: "```",
},
{
data: []byte("```"),
Accept info strings in code fences (#448) * Accept info strings in code fences According to the common mark standard, code fence info strings can be anything, not just single words. Update the tests and parser accordingly. The formatter already expected an info string with a language and HTML classes, so this does not need to change. Update the LaTeX formatter to take the first word of the info string as the language. Fixes #410 (in v1). * Don't output whole info string as code classes This follows the common mark specification. * run go fmt
2018-04-28 18:25:19 +08:00
infoRequested: true,
Improve fence line detection. Rename isFenceCode to isFenceLine, document it, add tests. Add support for making newline optional, this will be needed in future commits.
2016-07-16 02:41:27 +08:00
newlineOptional: true,
wantEnd: 3,
wantMarker: "```",
},
{
data: []byte("``` go"),
Accept info strings in code fences (#448) * Accept info strings in code fences According to the common mark standard, code fence info strings can be anything, not just single words. Update the tests and parser accordingly. The formatter already expected an info string with a language and HTML classes, so this does not need to change. Update the LaTeX formatter to take the first word of the info string as the language. Fixes #410 (in v1). * Don't output whole info string as code classes This follows the common mark specification. * run go fmt
2018-04-28 18:25:19 +08:00
infoRequested: true,
Improve fence line detection. Rename isFenceCode to isFenceLine, document it, add tests. Add support for making newline optional, this will be needed in future commits.
2016-07-16 02:41:27 +08:00
newlineOptional: true,
wantEnd: 6,
wantMarker: "```",
Accept info strings in code fences (#448) * Accept info strings in code fences According to the common mark standard, code fence info strings can be anything, not just single words. Update the tests and parser accordingly. The formatter already expected an info string with a language and HTML classes, so this does not need to change. Update the LaTeX formatter to take the first word of the info string as the language. Fixes #410 (in v1). * Don't output whole info string as code classes This follows the common mark specification. * run go fmt
2018-04-28 18:25:19 +08:00
wantInfo: "go",
},
{
data: []byte("``` go foo bar"),
infoRequested: true,
newlineOptional: true,
wantEnd: 14,
wantMarker: "```",
wantInfo: "go foo bar",
},
{
data: []byte("``` go foo bar "),
infoRequested: true,
newlineOptional: true,
wantEnd: 16,
wantMarker: "```",
wantInfo: "go foo bar",
Improve fence line detection. Rename isFenceCode to isFenceLine, document it, add tests. Add support for making newline optional, this will be needed in future commits.
2016-07-16 02:41:27 +08:00
},
}
for _, test := range tests {
Accept info strings in code fences (#448) * Accept info strings in code fences According to the common mark standard, code fence info strings can be anything, not just single words. Update the tests and parser accordingly. The formatter already expected an info string with a language and HTML classes, so this does not need to change. Update the LaTeX formatter to take the first word of the info string as the language. Fixes #410 (in v1). * Don't output whole info string as code classes This follows the common mark specification. * run go fmt
2018-04-28 18:25:19 +08:00
var info *string
if test.infoRequested {
info = new(string)
Improve fence line detection. Rename isFenceCode to isFenceLine, document it, add tests. Add support for making newline optional, this will be needed in future commits.
2016-07-16 02:41:27 +08:00
}
Accept info strings in code fences (#448) * Accept info strings in code fences According to the common mark standard, code fence info strings can be anything, not just single words. Update the tests and parser accordingly. The formatter already expected an info string with a language and HTML classes, so this does not need to change. Update the LaTeX formatter to take the first word of the info string as the language. Fixes #410 (in v1). * Don't output whole info string as code classes This follows the common mark specification. * run go fmt
2018-04-28 18:25:19 +08:00
end, marker := isFenceLine(test.data, info, "```", test.newlineOptional)
Improve fence line detection. Rename isFenceCode to isFenceLine, document it, add tests. Add support for making newline optional, this will be needed in future commits.
2016-07-16 02:41:27 +08:00
if got, want := end, test.wantEnd; got != want {
t.Errorf("got end %v, want %v", got, want)
}
if got, want := marker, test.wantMarker; got != want {
t.Errorf("got marker %q, want %q", got, want)
}
Accept info strings in code fences (#448) * Accept info strings in code fences According to the common mark standard, code fence info strings can be anything, not just single words. Update the tests and parser accordingly. The formatter already expected an info string with a language and HTML classes, so this does not need to change. Update the LaTeX formatter to take the first word of the info string as the language. Fixes #410 (in v1). * Don't output whole info string as code classes This follows the common mark specification. * run go fmt
2018-04-28 18:25:19 +08:00
if test.infoRequested {
if got, want := *info, test.wantInfo; got != want {
t.Errorf("got info %q, want %q", got, want)
Improve fence line detection. Rename isFenceCode to isFenceLine, document it, add tests. Add support for making newline optional, this will be needed in future commits.
2016-07-16 02:41:27 +08:00
}
}
}
}
modify testcase of joinLine. 1. delete testdata 'zhJoinLines.txt'. 2. move the testcase from markdown_test.go into block_test.go.
2017-03-17 17:21:30 +08:00
func TestJoinLines(t *testing.T) {
input := `# 标题
第一
行文字。
第
二
行文字。
`
result := `<h1>标题</h1>
<p>第一行文字。</p>
<p>第二行文字。</p>
`
opt := Options{Extensions: commonExtensions | EXTENSION_JOIN_LINES}
renderer := HtmlRenderer(commonHtmlFlags, "", "")
output := MarkdownOptions([]byte(input), renderer, opt)
if string(output) != result {
t.Error("output dose not match.")
}
}
Document SanitizedAnchorName algorithm, copy implementation. (#352) The goal of this change is to reduce number of non-standard library packages (repositories) that blackfriday imports from 1 to 0, and in turn, reduce the cost of importing blackfriday into other projects. Do so by documenting the algorithm of SanitizedAnchorName, and include a copy of the small function inside blackfriday itself. The same functionality continues to be available in the original location, github.com/shurcooL/sanitized_anchor_name.Create. It can be used by existing users and those that look for a small package, and don't need all of blackfriday functionality. Existing users of blackfriday can use the new SanitizedAnchorName function directly and avoid an extra package import. Resolves #350.
2017-05-09 14:07:14 +08:00
func TestSanitizedAnchorName(t *testing.T) {
tests := []struct {
text string
want string
}{
{
text: "This is a header",
want: "this-is-a-header",
},
{
text: "This is also a header",
want: "this-is-also-a-header",
},
{
text: "main.go",
want: "main-go",
},
{
text: "Article 123",
want: "article-123",
},
{
text: "<- Let's try this, shall we?",
want: "let-s-try-this-shall-we",
},
{
text: " ",
want: "",
},
{
text: "Hello, 世界",
want: "hello-世界",
},
}
for _, test := range tests {
if got := SanitizedAnchorName(test.text); got != test.want {
t.Errorf("SanitizedAnchorName(%q):\ngot %q\nwant %q", test.text, got, test.want)
}
}
}
Reference in New Issue Copy Permalink