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
119f356b88
blackfriday/inline_test.go

1177 lines
32 KiB
Go
Raw Normal View History

starting inline unit tests, fix a few minor bugs they exposed
2011-06-02 02:17:17 +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.
starting inline unit tests, fix a few minor bugs they exposed
2011-06-02 02:17:17 +08:00
//
//
// Unit tests for inline parsing
//
package blackfriday
import (
Add tests for new footnote functionality
2014-05-26 02:07:05 +08:00
"regexp"
starting inline unit tests, fix a few minor bugs they exposed
2011-06-02 02:17:17 +08:00
"testing"
Add tests for new footnote functionality
2014-05-26 02:07:05 +08:00
"strings"
starting inline unit tests, fix a few minor bugs they exposed
2011-06-02 02:17:17 +08:00
)
func TestEmphasis(t *testing.T) {
var tests = []string{
"nothing inline\n",
"<p>nothing inline</p>\n",
"simple *inline* test\n",
"<p>simple <em>inline</em> test</p>\n",
"*at the* beginning\n",
"<p><em>at the</em> beginning</p>\n",
"at the *end*\n",
"<p>at the <em>end</em></p>\n",
"*try two* in *one line*\n",
"<p><em>try two</em> in <em>one line</em></p>\n",
"over *two\nlines* test\n",
"<p>over <em>two\nlines</em> test</p>\n",
"odd *number of* markers* here\n",
"<p>odd <em>number of</em> markers* here</p>\n",
"odd *number\nof* markers* here\n",
"<p>odd <em>number\nof</em> markers* here</p>\n",
"simple _inline_ test\n",
"<p>simple <em>inline</em> test</p>\n",
"_at the_ beginning\n",
"<p><em>at the</em> beginning</p>\n",
"at the _end_\n",
"<p>at the <em>end</em></p>\n",
"_try two_ in _one line_\n",
"<p><em>try two</em> in <em>one line</em></p>\n",
"over _two\nlines_ test\n",
"<p>over <em>two\nlines</em> test</p>\n",
"odd _number of_ markers_ here\n",
"<p>odd <em>number of</em> markers_ here</p>\n",
"odd _number\nof_ markers_ here\n",
"<p>odd <em>number\nof</em> markers_ here</p>\n",
"mix of *markers_\n",
"<p>mix of *markers_</p>\n",
Fix escaping asterisks within emphasis First check for escaped character, *then* look if i-th character is an emphasis character. Closes #18.
2015-10-14 00:57:07 +08:00
"*What is A\\* algorithm?*\n",
"<p><em>What is A* algorithm?</em></p>\n",
starting inline unit tests, fix a few minor bugs they exposed
2011-06-02 02:17:17 +08:00
}
fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
doTestsInline(t, tests)
starting inline unit tests, fix a few minor bugs they exposed
2011-06-02 02:17:17 +08:00
}
Add programmable reference overrides If a user provides a ReferenceOverride function, then reference ids will be passed to the given ReferenceOverride function first, before consulting the generated reference table. The goal here is to enable programmable support for "WikiWords"-style identifiers or other application-specific user-generated keywords. Example, writing documentation: The [Frobnosticator][] is a very important class in our codebase. While it is used to frobnosticate widgets in general, it can also be passed to the [WeeDoodler][] to interesting effect. This might be solveable with the HTML Renderer relative prefix, but I didn't see a good way of making a short link to 'Frobnosticator' relatively without having to write it twice. Maybe '<Frobnosticator>' should work? Should Autolinks work for relative links? In addition, I wanted a little more richness. I plan to support Godoc links by prefixing references with a '!', like so: Check out the [Frobnosticator][] helper function [!util.Frobnosticate()][] The first link links to the Frobnosticator architectural overview documentation, whereas the second links to Godoc. Better advice on how to implement this sort of think with Blackfriday is highly desired.
2014-12-17 07:17:49 +08:00
func TestReferenceOverride(t *testing.T) {
var tests = []string{
"test [ref1][]\n",
"<p>test <a href=\"http://www.ref1.com/\" title=\"Reference 1\">ref1</a></p>\n",
"test [my ref][ref1]\n",
"<p>test <a href=\"http://www.ref1.com/\" title=\"Reference 1\">my ref</a></p>\n",
"test [ref2][]\n\n[ref2]: http://www.leftalone.com/ (Ref left alone)\n",
"<p>test <a href=\"http://www.overridden.com/\" title=\"Reference Overridden\">ref2</a></p>\n",
"test [ref3][]\n\n[ref3]: http://www.leftalone.com/ (Ref left alone)\n",
"<p>test <a href=\"http://www.leftalone.com/\" title=\"Ref left alone\">ref3</a></p>\n",
"test [ref4][]\n\n[ref4]: http://zombo.com/ (You can do anything)\n",
"<p>test [ref4][]</p>\n",
"test [!(*http.ServeMux).ServeHTTP][] complicated ref\n",
"<p>test <a href=\"http://localhost:6060/pkg/net/http/#ServeMux.ServeHTTP\" title=\"ServeHTTP docs\">!(*http.ServeMux).ServeHTTP</a> complicated ref</p>\n",
Add a missing test case for reference override Exercise link text override.
2015-05-06 20:57:15 +08:00
"test [ref5][]\n",
"<p>test <a href=\"http://www.ref5.com/\" title=\"Reference 5\">Moo</a></p>\n",
Add programmable reference overrides If a user provides a ReferenceOverride function, then reference ids will be passed to the given ReferenceOverride function first, before consulting the generated reference table. The goal here is to enable programmable support for "WikiWords"-style identifiers or other application-specific user-generated keywords. Example, writing documentation: The [Frobnosticator][] is a very important class in our codebase. While it is used to frobnosticate widgets in general, it can also be passed to the [WeeDoodler][] to interesting effect. This might be solveable with the HTML Renderer relative prefix, but I didn't see a good way of making a short link to 'Frobnosticator' relatively without having to write it twice. Maybe '<Frobnosticator>' should work? Should Autolinks work for relative links? In addition, I wanted a little more richness. I plan to support Godoc links by prefixing references with a '!', like so: Check out the [Frobnosticator][] helper function [!util.Frobnosticate()][] The first link links to the Frobnosticator architectural overview documentation, whereas the second links to Godoc. Better advice on how to implement this sort of think with Blackfriday is highly desired.
2014-12-17 07:17:49 +08:00
}
Wrap inline test parameters in a struct Take advantage of zero value initialization.
2016-04-04 16:18:50 +08:00
doTestsInlineParam(t, tests, TestParams{
Change the public interface to use functional options Convert the most important Blackfriday's function, Markdown(), to accept functional options (as per this Dave Cheney's post: https://dave.cheney.net/2014/10/17/functional-options-for-friendly-apis)
2017-02-02 15:35:10 +08:00
referenceOverride: func(reference string) (rv *Reference, overridden bool) {
switch reference {
case "ref1":
// just an overridden reference exists without definition
return &Reference{
Link: "http://www.ref1.com/",
Title: "Reference 1"}, true
case "ref2":
// overridden exists and reference defined
return &Reference{
Link: "http://www.overridden.com/",
Title: "Reference Overridden"}, true
case "ref3":
// not overridden and reference defined
Add programmable reference overrides If a user provides a ReferenceOverride function, then reference ids will be passed to the given ReferenceOverride function first, before consulting the generated reference table. The goal here is to enable programmable support for "WikiWords"-style identifiers or other application-specific user-generated keywords. Example, writing documentation: The [Frobnosticator][] is a very important class in our codebase. While it is used to frobnosticate widgets in general, it can also be passed to the [WeeDoodler][] to interesting effect. This might be solveable with the HTML Renderer relative prefix, but I didn't see a good way of making a short link to 'Frobnosticator' relatively without having to write it twice. Maybe '<Frobnosticator>' should work? Should Autolinks work for relative links? In addition, I wanted a little more richness. I plan to support Godoc links by prefixing references with a '!', like so: Check out the [Frobnosticator][] helper function [!util.Frobnosticate()][] The first link links to the Frobnosticator architectural overview documentation, whereas the second links to Godoc. Better advice on how to implement this sort of think with Blackfriday is highly desired.
2014-12-17 07:17:49 +08:00
return nil, false
Change the public interface to use functional options Convert the most important Blackfriday's function, Markdown(), to accept functional options (as per this Dave Cheney's post: https://dave.cheney.net/2014/10/17/functional-options-for-friendly-apis)
2017-02-02 15:35:10 +08:00
case "ref4":
// overridden missing and defined
return nil, true
case "!(*http.ServeMux).ServeHTTP":
return &Reference{
Link: "http://localhost:6060/pkg/net/http/#ServeMux.ServeHTTP",
Title: "ServeHTTP docs"}, true
case "ref5":
return &Reference{
Link: "http://www.ref5.com/",
Title: "Reference 5",
Text: "Moo",
}, true
}
return nil, false
Wrap inline test parameters in a struct Take advantage of zero value initialization.
2016-04-04 16:18:50 +08:00
},
})
Add programmable reference overrides If a user provides a ReferenceOverride function, then reference ids will be passed to the given ReferenceOverride function first, before consulting the generated reference table. The goal here is to enable programmable support for "WikiWords"-style identifiers or other application-specific user-generated keywords. Example, writing documentation: The [Frobnosticator][] is a very important class in our codebase. While it is used to frobnosticate widgets in general, it can also be passed to the [WeeDoodler][] to interesting effect. This might be solveable with the HTML Renderer relative prefix, but I didn't see a good way of making a short link to 'Frobnosticator' relatively without having to write it twice. Maybe '<Frobnosticator>' should work? Should Autolinks work for relative links? In addition, I wanted a little more richness. I plan to support Godoc links by prefixing references with a '!', like so: Check out the [Frobnosticator][] helper function [!util.Frobnosticate()][] The first link links to the Frobnosticator architectural overview documentation, whereas the second links to Godoc. Better advice on how to implement this sort of think with Blackfriday is highly desired.
2014-12-17 07:17:49 +08:00
}
starting inline unit tests, fix a few minor bugs they exposed
2011-06-02 02:17:17 +08:00
func TestStrong(t *testing.T) {
var tests = []string{
"nothing inline\n",
"<p>nothing inline</p>\n",
"simple **inline** test\n",
"<p>simple <strong>inline</strong> test</p>\n",
"**at the** beginning\n",
"<p><strong>at the</strong> beginning</p>\n",
"at the **end**\n",
"<p>at the <strong>end</strong></p>\n",
"**try two** in **one line**\n",
"<p><strong>try two</strong> in <strong>one line</strong></p>\n",
"over **two\nlines** test\n",
"<p>over <strong>two\nlines</strong> test</p>\n",
"odd **number of** markers** here\n",
"<p>odd <strong>number of</strong> markers** here</p>\n",
"odd **number\nof** markers** here\n",
"<p>odd <strong>number\nof</strong> markers** here</p>\n",
"simple __inline__ test\n",
"<p>simple <strong>inline</strong> test</p>\n",
"__at the__ beginning\n",
"<p><strong>at the</strong> beginning</p>\n",
"at the __end__\n",
"<p>at the <strong>end</strong></p>\n",
"__try two__ in __one line__\n",
"<p><strong>try two</strong> in <strong>one line</strong></p>\n",
"over __two\nlines__ test\n",
"<p>over <strong>two\nlines</strong> test</p>\n",
"odd __number of__ markers__ here\n",
"<p>odd <strong>number of</strong> markers__ here</p>\n",
"odd __number\nof__ markers__ here\n",
"<p>odd <strong>number\nof</strong> markers__ here</p>\n",
"mix of **markers__\n",
"<p>mix of **markers__</p>\n",
Fix bug parsing emphasis Start searching for emphasis character at 0th index instead of 1st. Fixes a corner case with doubly emphasised code span followed by another code span on the same line. Changes interpretation of improperly nested emphasis, hence the change in TestEmphasisMix(). Closes #156.
2015-10-13 02:06:27 +08:00
"**`/usr`** : this folder is named `usr`\n",
"<p><strong><code>/usr</code></strong> : this folder is named <code>usr</code></p>\n",
"**`/usr`** :\n\n this folder is named `usr`\n",
"<p><strong><code>/usr</code></strong> :</p>\n\n<p>this folder is named <code>usr</code></p>\n",
starting inline unit tests, fix a few minor bugs they exposed
2011-06-02 02:17:17 +08:00
}
fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
doTestsInline(t, tests)
starting inline unit tests, fix a few minor bugs they exposed
2011-06-02 02:17:17 +08:00
}
func TestEmphasisMix(t *testing.T) {
var tests = []string{
"***triple emphasis***\n",
"<p><strong><em>triple emphasis</em></strong></p>\n",
"***triple\nemphasis***\n",
"<p><strong><em>triple\nemphasis</em></strong></p>\n",
"___triple emphasis___\n",
"<p><strong><em>triple emphasis</em></strong></p>\n",
"***triple emphasis___\n",
"<p>***triple emphasis___</p>\n",
"*__triple emphasis__*\n",
"<p><em><strong>triple emphasis</strong></em></p>\n",
"__*triple emphasis*__\n",
"<p><strong><em>triple emphasis</em></strong></p>\n",
"**improper *nesting** is* bad\n",
"<p><strong>improper *nesting</strong> is* bad</p>\n",
"*improper **nesting* is** bad\n",
Fix bug parsing emphasis Start searching for emphasis character at 0th index instead of 1st. Fixes a corner case with doubly emphasised code span followed by another code span on the same line. Changes interpretation of improperly nested emphasis, hence the change in TestEmphasisMix(). Closes #156.
2015-10-13 02:06:27 +08:00
"<p>*improper <strong>nesting* is</strong> bad</p>\n",
starting inline unit tests, fix a few minor bugs they exposed
2011-06-02 02:17:17 +08:00
}
fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
doTestsInline(t, tests)
starting inline unit tests, fix a few minor bugs they exposed
2011-06-02 02:17:17 +08:00
}
add tests for emphasis with links
2014-12-25 05:05:29 +08:00
func TestEmphasisLink(t *testing.T) {
var tests = []string{
"[first](before) *text[second] (inside)text* [third](after)\n",
"<p><a href=\"before\">first</a> <em>text<a href=\"inside\">second</a>text</em> <a href=\"after\">third</a></p>\n",
"*incomplete [link] definition*\n",
"<p><em>incomplete [link] definition</em></p>\n",
"*it's [emphasis*] (not link)\n",
"<p><em>it's [emphasis</em>] (not link)</p>\n",
"*it's [emphasis*] and *[asterisk]\n",
"<p><em>it's [emphasis</em>] and *[asterisk]</p>\n",
}
doTestsInline(t, tests)
}
starting inline unit tests, fix a few minor bugs they exposed
2011-06-02 02:17:17 +08:00
func TestStrikeThrough(t *testing.T) {
var tests = []string{
"nothing inline\n",
"<p>nothing inline</p>\n",
"simple ~~inline~~ test\n",
"<p>simple <del>inline</del> test</p>\n",
"~~at the~~ beginning\n",
"<p><del>at the</del> beginning</p>\n",
"at the ~~end~~\n",
"<p>at the <del>end</del></p>\n",
"~~try two~~ in ~~one line~~\n",
"<p><del>try two</del> in <del>one line</del></p>\n",
"over ~~two\nlines~~ test\n",
"<p>over <del>two\nlines</del> test</p>\n",
"odd ~~number of~~ markers~~ here\n",
"<p>odd <del>number of</del> markers~~ here</p>\n",
"odd ~~number\nof~~ markers~~ here\n",
"<p>odd <del>number\nof</del> markers~~ here</p>\n",
}
fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
doTestsInline(t, tests)
starting inline unit tests, fix a few minor bugs they exposed
2011-06-02 02:17:17 +08:00
}
func TestCodeSpan(t *testing.T) {
var tests = []string{
"`source code`\n",
"<p><code>source code</code></p>\n",
"` source code with spaces `\n",
"<p><code>source code with spaces</code></p>\n",
"` source code with spaces `not here\n",
"<p><code>source code with spaces</code>not here</p>\n",
"a `single marker\n",
"<p>a `single marker</p>\n",
"a single multi-tick marker with ``` no text\n",
"<p>a single multi-tick marker with ``` no text</p>\n",
"markers with ` ` a space\n",
move whitespace stripping to parser, not renderers
2011-06-30 05:38:35 +08:00
"<p>markers with a space</p>\n",
starting inline unit tests, fix a few minor bugs they exposed
2011-06-02 02:17:17 +08:00
"`source code` and a `stray\n",
"<p><code>source code</code> and a `stray</p>\n",
unit test for linebreaks
2011-06-02 08:52:55 +08:00
"`source *with* _awkward characters_ in it`\n",
"<p><code>source *with* _awkward characters_ in it</code></p>\n",
starting inline unit tests, fix a few minor bugs they exposed
2011-06-02 02:17:17 +08:00
"`split over\ntwo lines`\n",
"<p><code>split over\ntwo lines</code></p>\n",
"```multiple ticks``` for the marker\n",
"<p><code>multiple ticks</code> for the marker</p>\n",
"```multiple ticks `with` ticks inside```\n",
"<p><code>multiple ticks `with` ticks inside</code></p>\n",
}
fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
doTestsInline(t, tests)
starting inline unit tests, fix a few minor bugs they exposed
2011-06-02 02:17:17 +08:00
}
unit test for linebreaks
2011-06-02 08:52:55 +08:00
func TestLineBreak(t *testing.T) {
var tests = []string{
"this line \nhas a break\n",
"<p>this line<br />\nhas a break</p>\n",
"this line \ndoes not\n",
more robust whitespace stripping and matching corrections to tests
2011-06-28 06:06:16 +08:00
"<p>this line\ndoes not</p>\n",
unit test for linebreaks
2011-06-02 08:52:55 +08:00
Added test for backslash line break
2015-04-23 16:49:08 +08:00
"this line\\\ndoes not\n",
"<p>this line\\\ndoes not</p>\n",
"this line\\ \ndoes not\n",
"<p>this line\\\ndoes not</p>\n",
unit test for linebreaks
2011-06-02 08:52:55 +08:00
"this has an \nextra space\n",
"<p>this has an<br />\nextra space</p>\n",
}
fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
doTestsInline(t, tests)
Added test for backslash line break
2015-04-23 16:49:08 +08:00
tests = []string{
"this line \nhas a break\n",
"<p>this line<br />\nhas a break</p>\n",
"this line \ndoes not\n",
"<p>this line\ndoes not</p>\n",
"this line\\\nhas a break\n",
"<p>this line<br />\nhas a break</p>\n",
"this line\\ \ndoes not\n",
"<p>this line\\\ndoes not</p>\n",
"this has an \nextra space\n",
"<p>this has an<br />\nextra space</p>\n",
}
Change the public interface to use functional options Convert the most important Blackfriday's function, Markdown(), to accept functional options (as per this Dave Cheney's post: https://dave.cheney.net/2014/10/17/functional-options-for-friendly-apis)
2017-02-02 15:35:10 +08:00
doTestsInlineParam(t, tests, TestParams{
extensions: BackslashLineBreak})
unit test for linebreaks
2011-06-02 08:52:55 +08:00
}
more inline unit tests
2011-06-25 06:39:50 +08:00
func TestInlineLink(t *testing.T) {
var tests = []string{
"[foo](/bar/)\n",
"<p><a href=\"/bar/\">foo</a></p>\n",
"[foo with a title](/bar/ \"title\")\n",
"<p><a href=\"/bar/\" title=\"title\">foo with a title</a></p>\n",
"[foo with a title](/bar/\t\"title\")\n",
"<p><a href=\"/bar/\" title=\"title\">foo with a title</a></p>\n",
"[foo with a title](/bar/ \"title\" )\n",
"<p><a href=\"/bar/\" title=\"title\">foo with a title</a></p>\n",
"[foo with a title](/bar/ title with no quotes)\n",
"<p><a href=\"/bar/ title with no quotes\">foo with a title</a></p>\n",
"[foo]()\n",
simplify inline callback interface
2011-06-30 03:00:54 +08:00
"<p>[foo]()</p>\n",
more inline unit tests
2011-06-25 06:39:50 +08:00
"![foo](/bar/)\n",
Do not emit newline after <img> tag. This changes HTML renderer not to always add a newline character after <img> tags. This is desirable because <img> tags can be inlined, and sometimes you want to avoid whitespace on left and right sides. Previous behavior of always adding a newline would unavoidably create whitespace after <img> tag. Update all tests to match new behavior. There are few changes, and they're completely isolated to inline image tests. Fixes #169.
2015-05-26 03:41:06 +08:00
"<p><img src=\"/bar/\" alt=\"foo\" /></p>\n",
more inline unit tests
2011-06-25 06:39:50 +08:00
"![foo with a title](/bar/ \"title\")\n",
Do not emit newline after <img> tag. This changes HTML renderer not to always add a newline character after <img> tags. This is desirable because <img> tags can be inlined, and sometimes you want to avoid whitespace on left and right sides. Previous behavior of always adding a newline would unavoidably create whitespace after <img> tag. Update all tests to match new behavior. There are few changes, and they're completely isolated to inline image tests. Fixes #169.
2015-05-26 03:41:06 +08:00
"<p><img src=\"/bar/\" alt=\"foo with a title\" title=\"title\" /></p>\n",
more inline unit tests
2011-06-25 06:39:50 +08:00
"![foo with a title](/bar/\t\"title\")\n",
Do not emit newline after <img> tag. This changes HTML renderer not to always add a newline character after <img> tags. This is desirable because <img> tags can be inlined, and sometimes you want to avoid whitespace on left and right sides. Previous behavior of always adding a newline would unavoidably create whitespace after <img> tag. Update all tests to match new behavior. There are few changes, and they're completely isolated to inline image tests. Fixes #169.
2015-05-26 03:41:06 +08:00
"<p><img src=\"/bar/\" alt=\"foo with a title\" title=\"title\" /></p>\n",
more inline unit tests
2011-06-25 06:39:50 +08:00
"![foo with a title](/bar/ \"title\" )\n",
Do not emit newline after <img> tag. This changes HTML renderer not to always add a newline character after <img> tags. This is desirable because <img> tags can be inlined, and sometimes you want to avoid whitespace on left and right sides. Previous behavior of always adding a newline would unavoidably create whitespace after <img> tag. Update all tests to match new behavior. There are few changes, and they're completely isolated to inline image tests. Fixes #169.
2015-05-26 03:41:06 +08:00
"<p><img src=\"/bar/\" alt=\"foo with a title\" title=\"title\" /></p>\n",
more inline unit tests
2011-06-25 06:39:50 +08:00
"![foo with a title](/bar/ title with no quotes)\n",
Do not emit newline after <img> tag. This changes HTML renderer not to always add a newline character after <img> tags. This is desirable because <img> tags can be inlined, and sometimes you want to avoid whitespace on left and right sides. Previous behavior of always adding a newline would unavoidably create whitespace after <img> tag. Update all tests to match new behavior. There are few changes, and they're completely isolated to inline image tests. Fixes #169.
2015-05-26 03:41:06 +08:00
"<p><img src=\"/bar/ title with no quotes\" alt=\"foo with a title\" /></p>\n",
more inline unit tests
2011-06-25 06:39:50 +08:00
Make sure relative URLs are preserved Add tests to make sure we don't break relative URLs again. Extracted common html flags and common extensions for easy access from tests. Closes issue #104, which was fixed as a side effect of cf6bfc9.
2014-09-21 21:29:24 +08:00
"![](img.jpg)\n",
Do not emit newline after <img> tag. This changes HTML renderer not to always add a newline character after <img> tags. This is desirable because <img> tags can be inlined, and sometimes you want to avoid whitespace on left and right sides. Previous behavior of always adding a newline would unavoidably create whitespace after <img> tag. Update all tests to match new behavior. There are few changes, and they're completely isolated to inline image tests. Fixes #169.
2015-05-26 03:41:06 +08:00
"<p><img src=\"img.jpg\" alt=\"\" /></p>\n",
Make sure relative URLs are preserved Add tests to make sure we don't break relative URLs again. Extracted common html flags and common extensions for easy access from tests. Closes issue #104, which was fixed as a side effect of cf6bfc9.
2014-09-21 21:29:24 +08:00
"[link](url)\n",
"<p><a href=\"url\">link</a></p>\n",
more inline unit tests
2011-06-25 06:39:50 +08:00
"![foo]()\n",
simplify inline callback interface
2011-06-30 03:00:54 +08:00
"<p>![foo]()</p>\n",
more inline unit tests
2011-06-25 06:39:50 +08:00
"[a link]\t(/with_a_tab/)\n",
"<p><a href=\"/with_a_tab/\">a link</a></p>\n",
"[a link] (/with_spaces/)\n",
"<p><a href=\"/with_spaces/\">a link</a></p>\n",
"[text (with) [[nested] (brackets)]](/url/)\n",
"<p><a href=\"/url/\">text (with) [[nested] (brackets)]</a></p>\n",
"[text (with) [broken nested] (brackets)]](/url/)\n",
"<p>[text (with) <a href=\"brackets\">broken nested</a>]](/url/)</p>\n",
"[text\nwith a newline](/link/)\n",
"<p><a href=\"/link/\">text\nwith a newline</a></p>\n",
"[text in brackets] [followed](/by a link/)\n",
"<p>[text in brackets] <a href=\"/by a link/\">followed</a></p>\n",
"[link with\\] a closing bracket](/url/)\n",
"<p><a href=\"/url/\">link with] a closing bracket</a></p>\n",
"[link with\\[ an opening bracket](/url/)\n",
"<p><a href=\"/url/\">link with[ an opening bracket</a></p>\n",
"[link with\\) a closing paren](/url/)\n",
"<p><a href=\"/url/\">link with) a closing paren</a></p>\n",
"[link with\\( an opening paren](/url/)\n",
"<p><a href=\"/url/\">link with( an opening paren</a></p>\n",
"[link]( with whitespace)\n",
"<p><a href=\"with whitespace\">link</a></p>\n",
"[link]( with whitespace )\n",
"<p><a href=\"with whitespace\">link</a></p>\n",
Added test for link inside image
2013-09-09 13:51:20 +08:00
"[![image](someimage)](with image)\n",
Do not emit newline after <img> tag. This changes HTML renderer not to always add a newline character after <img> tags. This is desirable because <img> tags can be inlined, and sometimes you want to avoid whitespace on left and right sides. Previous behavior of always adding a newline would unavoidably create whitespace after <img> tag. Update all tests to match new behavior. There are few changes, and they're completely isolated to inline image tests. Fixes #169.
2015-05-26 03:41:06 +08:00
"<p><a href=\"with image\"><img src=\"someimage\" alt=\"image\" /></a></p>\n",
Added test for link inside image
2013-09-09 13:51:20 +08:00
more inline unit tests
2011-06-25 06:39:50 +08:00
"[link](url \"one quote)\n",
"<p><a href=\"url &quot;one quote\">link</a></p>\n",
"[link](url 'one quote)\n",
"<p><a href=\"url 'one quote\">link</a></p>\n",
"[link](<url>)\n",
"<p><a href=\"url\">link</a></p>\n",
"[link & ampersand](/url/)\n",
"<p><a href=\"/url/\">link &amp; ampersand</a></p>\n",
"[link &amp; ampersand](/url/)\n",
"<p><a href=\"/url/\">link &amp; ampersand</a></p>\n",
"[link](/url/&query)\n",
"<p><a href=\"/url/&amp;query\">link</a></p>\n",
panic fix (issue #33) with test case
2013-09-12 02:47:43 +08:00
"[[t]](/t)\n",
"<p><a href=\"/t\">[t]</a></p>\n",
update about links when link to current directory or parent directory
2015-02-20 17:06:55 +08:00
"[link](</>)\n",
"<p><a href=\"/\">link</a></p>\n",
"[link](<./>)\n",
"<p><a href=\"./\">link</a></p>\n",
"[link](<../>)\n",
"<p><a href=\"../\">link</a></p>\n",
more inline unit tests
2011-06-25 06:39:50 +08:00
}
Add tests for absolute prefix
2014-05-26 02:22:33 +08:00
doLinkTestsInline(t, tests)
more inline unit tests
2011-06-25 06:39:50 +08:00
}
add rel="noreferrer" option
2015-03-15 07:46:32 +08:00
func TestRelAttrLink(t *testing.T) {
var nofollowTests = []string{
test: add nofollow ref for non internal links only
2014-03-21 11:17:31 +08:00
"[foo](http://bar.com/foo/)\n",
"<p><a href=\"http://bar.com/foo/\" rel=\"nofollow\">foo</a></p>\n",
Rip off all blackfriday's html sanitization effort As per discussion in issue #90.
2014-09-20 01:30:00 +08:00
Merge branch 'master' of github.com:gihnius/blackfriday into gihnius-master Conflicts: html.go inline_test.go
2014-05-02 02:43:42 +08:00
"[foo](/bar/)\n",
"<p><a href=\"/bar/\">foo</a></p>\n",
update about links when link to current directory or parent directory
2015-02-20 17:06:55 +08:00
"[foo](/)\n",
"<p><a href=\"/\">foo</a></p>\n",
"[foo](./)\n",
"<p><a href=\"./\">foo</a></p>\n",
"[foo](../)\n",
"<p><a href=\"../\">foo</a></p>\n",
"[foo](../bar)\n",
"<p><a href=\"../bar\">foo</a></p>\n",
Merge branch 'master' of github.com:gihnius/blackfriday into gihnius-master Conflicts: html.go inline_test.go
2014-05-02 02:43:42 +08:00
}
Wrap inline test parameters in a struct Take advantage of zero value initialization.
2016-04-04 16:18:50 +08:00
doTestsInlineParam(t, nofollowTests, TestParams{
HTMLFlags: Safelink | NofollowLinks,
})
add rel="noreferrer" option
2015-03-15 07:46:32 +08:00
var noreferrerTests = []string{
"[foo](http://bar.com/foo/)\n",
"<p><a href=\"http://bar.com/foo/\" rel=\"noreferrer\">foo</a></p>\n",
"[foo](/bar/)\n",
"<p><a href=\"/bar/\">foo</a></p>\n",
}
Wrap inline test parameters in a struct Take advantage of zero value initialization.
2016-04-04 16:18:50 +08:00
doTestsInlineParam(t, noreferrerTests, TestParams{
HTMLFlags: Safelink | NoreferrerLinks,
})
add rel="noreferrer" option
2015-03-15 07:46:32 +08:00
var nofollownoreferrerTests = []string{
"[foo](http://bar.com/foo/)\n",
"<p><a href=\"http://bar.com/foo/\" rel=\"nofollow noreferrer\">foo</a></p>\n",
"[foo](/bar/)\n",
"<p><a href=\"/bar/\">foo</a></p>\n",
}
Wrap inline test parameters in a struct Take advantage of zero value initialization.
2016-04-04 16:18:50 +08:00
doTestsInlineParam(t, nofollownoreferrerTests, TestParams{
HTMLFlags: Safelink | NofollowLinks | NoreferrerLinks,
})
add HTML_NOFOLLOW_LINKS
2014-02-25 22:21:57 +08:00
}
add target blank attr
2014-03-21 10:52:46 +08:00
func TestHrefTargetBlank(t *testing.T) {
var tests = []string{
Add support for a bunch more safe HTML element tags, and bring them into some order.
2014-05-02 04:08:32 +08:00
// internal link
add target blank attr
2014-03-21 10:52:46 +08:00
"[foo](/bar/)\n",
"<p><a href=\"/bar/\">foo</a></p>\n",
update about links when link to current directory or parent directory
2015-02-20 17:06:55 +08:00
"[foo](/)\n",
"<p><a href=\"/\">foo</a></p>\n",
"[foo](./)\n",
"<p><a href=\"./\">foo</a></p>\n",
"[foo](./bar)\n",
"<p><a href=\"./bar\">foo</a></p>\n",
"[foo](../)\n",
"<p><a href=\"../\">foo</a></p>\n",
"[foo](../bar)\n",
"<p><a href=\"../bar\">foo</a></p>\n",
add target blank attr
2014-03-21 10:52:46 +08:00
"[foo](http://example.com)\n",
"<p><a href=\"http://example.com\" target=\"_blank\">foo</a></p>\n",
}
Wrap inline test parameters in a struct Take advantage of zero value initialization.
2016-04-04 16:18:50 +08:00
doTestsInlineParam(t, tests, TestParams{
HTMLFlags: Safelink | HrefTargetBlank,
})
add HTML_NOFOLLOW_LINKS
2014-02-25 22:21:57 +08:00
}
Tests for links when using HTML_SAFELINK
2013-12-19 18:00:47 +08:00
func TestSafeInlineLink(t *testing.T) {
var tests = []string{
"[foo](/bar/)\n",
"<p><a href=\"/bar/\">foo</a></p>\n",
update about links when link to current directory or parent directory
2015-02-20 17:06:55 +08:00
"[foo](/)\n",
"<p><a href=\"/\">foo</a></p>\n",
"[foo](./)\n",
"<p><a href=\"./\">foo</a></p>\n",
"[foo](../)\n",
"<p><a href=\"../\">foo</a></p>\n",
Tests for links when using HTML_SAFELINK
2013-12-19 18:00:47 +08:00
"[foo](http://bar/)\n",
"<p><a href=\"http://bar/\">foo</a></p>\n",
"[foo](https://bar/)\n",
"<p><a href=\"https://bar/\">foo</a></p>\n",
"[foo](ftp://bar/)\n",
"<p><a href=\"ftp://bar/\">foo</a></p>\n",
"[foo](mailto://bar/)\n",
"<p><a href=\"mailto://bar/\">foo</a></p>\n",
// Not considered safe
"[foo](baz://bar/)\n",
"<p><tt>foo</tt></p>\n",
}
doSafeTestsInline(t, tests)
}
more inline unit tests
2011-06-25 06:39:50 +08:00
func TestReferenceLink(t *testing.T) {
var tests = []string{
"[link][ref]\n",
"<p>[link][ref]</p>\n",
"[link][ref]\n [ref]: /url/ \"title\"\n",
"<p><a href=\"/url/\" title=\"title\">link</a></p>\n",
"[link][ref]\n [ref]: /url/\n",
"<p><a href=\"/url/\">link</a></p>\n",
" [ref]: /url/\n",
"",
" [ref]: /url/\n[ref2]: /url/\n [ref3]: /url/\n",
"",
" [ref]: /url/\n[ref2]: /url/\n [ref3]: /url/\n [4spaces]: /url/\n",
"<pre><code>[4spaces]: /url/\n</code></pre>\n",
"[hmm](ref2)\n [ref]: /url/\n[ref2]: /url/\n [ref3]: /url/\n",
"<p><a href=\"ref2\">hmm</a></p>\n",
"[ref]\n",
"<p>[ref]</p>\n",
"[ref]\n [ref]: /url/ \"title\"\n",
"<p><a href=\"/url/\" title=\"title\">ref</a></p>\n",
update about links when link to current directory or parent directory
2015-02-20 17:06:55 +08:00
"[ref]\n [ref]: ../url/ \"title\"\n",
"<p><a href=\"../url/\" title=\"title\">ref</a></p>\n",
Fix #180 again The check was introduced with d28de22, when fixing #172 and #173. Then I removed it with bcd6dd8 when fixing #180 And then it was reintroduced with 232d06c when fixing regression. It seems that the check can be removed again. All these cases now have tests (including the one from 69f51af, which seems to have landed to v1 only, copying it here) and they all pass.
2017-02-12 23:57:51 +08:00
"[link][ref]\n [ref]: /url/",
"<p><a href=\"/url/\">link</a></p>\n",
more inline unit tests
2011-06-25 06:39:50 +08:00
}
Add tests for absolute prefix
2014-05-26 02:22:33 +08:00
doLinkTestsInline(t, tests)
more inline unit tests
2011-06-25 06:39:50 +08:00
}
func TestTags(t *testing.T) {
var tests = []string{
"a <span>tag</span>\n",
"<p>a <span>tag</span></p>\n",
"<span>tag</span>\n",
"<p><span>tag</span></p>\n",
"<span>mismatch</spandex>\n",
"<p><span>mismatch</spandex></p>\n",
"a <singleton /> tag\n",
"<p>a <singleton /> tag</p>\n",
}
fixed headers nested in lists, added prefix header unit tests
2011-06-28 00:13:13 +08:00
doTestsInline(t, tests)
more inline unit tests
2011-06-25 06:39:50 +08:00
}
func TestAutoLink(t *testing.T) {
var tests = []string{
add testcase for GFM autolink
2013-08-09 17:24:26 +08:00
"http://foo.com/\n",
"<p><a href=\"http://foo.com/\">http://foo.com/</a></p>\n",
"1 http://foo.com/\n",
"<p>1 <a href=\"http://foo.com/\">http://foo.com/</a></p>\n",
"1http://foo.com/\n",
"<p>1<a href=\"http://foo.com/\">http://foo.com/</a></p>\n",
"1.http://foo.com/\n",
"<p>1.<a href=\"http://foo.com/\">http://foo.com/</a></p>\n",
"1. http://foo.com/\n",
"<ol>\n<li><a href=\"http://foo.com/\">http://foo.com/</a></li>\n</ol>\n",
"-http://foo.com/\n",
"<p>-<a href=\"http://foo.com/\">http://foo.com/</a></p>\n",
"- http://foo.com/\n",
"<ul>\n<li><a href=\"http://foo.com/\">http://foo.com/</a></li>\n</ul>\n",
"_http://foo.com/\n",
"<p>_<a href=\"http://foo.com/\">http://foo.com/</a></p>\n",
"令狐http://foo.com/\n",
"<p>令狐<a href=\"http://foo.com/\">http://foo.com/</a></p>\n",
"令狐 http://foo.com/\n",
"<p>令狐 <a href=\"http://foo.com/\">http://foo.com/</a></p>\n",
"ahttp://foo.com/\n",
"<p>ahttp://foo.com/</p>\n",
">http://foo.com/\n",
"<blockquote>\n<p><a href=\"http://foo.com/\">http://foo.com/</a></p>\n</blockquote>\n",
"> http://foo.com/\n",
"<blockquote>\n<p><a href=\"http://foo.com/\">http://foo.com/</a></p>\n</blockquote>\n",
more inline unit tests
2011-06-25 06:39:50 +08:00
"go to <http://foo.com/>\n",
"<p>go to <a href=\"http://foo.com/\">http://foo.com/</a></p>\n",
"a secure <https://link.org>\n",
"<p>a secure <a href=\"https://link.org\">https://link.org</a></p>\n",
"an email <mailto:some@one.com>\n",
"<p>an email <a href=\"mailto:some@one.com\">some@one.com</a></p>\n",
"an email <mailto://some@one.com>\n",
"<p>an email <a href=\"mailto://some@one.com\">some@one.com</a></p>\n",
"an email <some@one.com>\n",
"<p>an email <a href=\"mailto:some@one.com\">some@one.com</a></p>\n",
"an ftp <ftp://old.com>\n",
"<p>an ftp <a href=\"ftp://old.com\">ftp://old.com</a></p>\n",
"an ftp <ftp:old.com>\n",
"<p>an ftp <a href=\"ftp:old.com\">ftp:old.com</a></p>\n",
"a link with <http://new.com?query=foo&bar>\n",
"<p>a link with <a href=\"http://new.com?query=foo&amp;bar\">" +
"http://new.com?query=foo&amp;bar</a></p>\n",
"quotes mean a tag <http://new.com?query=\"foo\"&bar>\n",
"<p>quotes mean a tag <http://new.com?query=\"foo\"&bar></p>\n",
"quotes mean a tag <http://new.com?query='foo'&bar>\n",
"<p>quotes mean a tag <http://new.com?query='foo'&bar></p>\n",
"unless escaped <http://new.com?query=\\\"foo\\\"&bar>\n",
"<p>unless escaped <a href=\"http://new.com?query=&quot;foo&quot;&amp;bar\">" +
"http://new.com?query=&quot;foo&quot;&amp;bar</a></p>\n",
"even a > can be escaped <http://new.com?q=\\>&etc>\n",
"<p>even a &gt; can be escaped <a href=\"http://new.com?q=&gt;&amp;etc\">" +
"http://new.com?q=&gt;&amp;etc</a></p>\n",
Fix bug with overzealous autolink processing When the source Markdown contains an anchor tag with URL as link text (i.e. <a href=...>http://foo.bar</a>), autolink converts that link text into another anchor tag, which is nonsense. Detect this situation with regexp and early exit autolink processing.
2014-01-26 03:42:34 +08:00
"<a href=\"http://fancy.com\">http://fancy.com</a>\n",
"<p><a href=\"http://fancy.com\">http://fancy.com</a></p>\n",
"<a href=\"http://fancy.com\">This is a link</a>\n",
"<p><a href=\"http://fancy.com\">This is a link</a></p>\n",
"<a href=\"http://www.fancy.com/A_B.pdf\">http://www.fancy.com/A_B.pdf</a>\n",
"<p><a href=\"http://www.fancy.com/A_B.pdf\">http://www.fancy.com/A_B.pdf</a></p>\n",
"(<a href=\"http://www.fancy.com/A_B\">http://www.fancy.com/A_B</a> (\n",
"<p>(<a href=\"http://www.fancy.com/A_B\">http://www.fancy.com/A_B</a> (</p>\n",
"(<a href=\"http://www.fancy.com/A_B\">http://www.fancy.com/A_B</a> (part two: <a href=\"http://www.fancy.com/A_B\">http://www.fancy.com/A_B</a>)).\n",
"<p>(<a href=\"http://www.fancy.com/A_B\">http://www.fancy.com/A_B</a> (part two: <a href=\"http://www.fancy.com/A_B\">http://www.fancy.com/A_B</a>)).</p>\n",
Fix bug in autolink termination Detect the end of link when it is immediately followed by an element.
2014-01-26 03:59:38 +08:00
"http://www.foo.com<br />\n",
"<p><a href=\"http://www.foo.com\">http://www.foo.com</a><br /></p>\n",
Fix bug in autolink overescaping html entities If autolink encounters a link which already has an escaped html entity, it would escape the ampersand again, producing things like these: &amp; --> &amp;amp; &quot; --> &amp;quot; This commit solves that by first looking for all entity-looking things in the link and copying those ranges verbatim, only considering the rest of the string for escaping. Doesn't seem to have considerable performance impact. The mailto: links are processed the old way.
2014-01-27 03:39:38 +08:00
"http://foo.com/viewtopic.php?f=18&amp;t=297",
"<p><a href=\"http://foo.com/viewtopic.php?f=18&amp;t=297\">http://foo.com/viewtopic.php?f=18&amp;t=297</a></p>\n",
"http://foo.com/viewtopic.php?param=&quot;18&quot;zz",
"<p><a href=\"http://foo.com/viewtopic.php?param=&quot;18&quot;zz\">http://foo.com/viewtopic.php?param=&quot;18&quot;zz</a></p>\n",
Fix bug in autolink with trailing semicolon In case the link ends with escaped html entity, the semicolon is a part of the link and should not be interpreted as punctuation.
2014-01-27 05:40:26 +08:00
"http://foo.com/viewtopic.php?param=&quot;18&quot;",
"<p><a href=\"http://foo.com/viewtopic.php?param=&quot;18&quot;\">http://foo.com/viewtopic.php?param=&quot;18&quot;</a></p>\n",
Remove last call to Truncate() from parser Autolink detection used to be triggered by a colon and preceding protocol name used to be rewound. Now instead of doing that, trigger autolink processing on [hmfHMF] and see if it looks like a link.
2015-10-28 03:56:16 +08:00
"<a href=\"https://fancy.com\">https://fancy.com</a>\n",
"<p><a href=\"https://fancy.com\">https://fancy.com</a></p>\n",
more inline unit tests
2011-06-25 06:39:50 +08:00
}
Add tests for absolute prefix
2014-05-26 02:22:33 +08:00
doLinkTestsInline(t, tests)
more inline unit tests
2011-06-25 06:39:50 +08:00
}
First attempt at supporting Pandoc-style footnotes. The existing tests have not broken but the new functionality does not work yet.
2013-06-25 09:18:47 +08:00
Add tests for new footnote functionality
2014-05-26 02:07:05 +08:00
var footnoteTests = []string{
Move footnote prefix to a better place
2014-05-25 03:28:37 +08:00
"testing footnotes.[^a]\n\n[^a]: This is the note\n",
`<p>testing footnotes.<sup class="footnote-ref" id="fnref:a"><a rel="footnote" href="#fn:a">1</a></sup></p>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
new tests pass but old tests now fail...
2013-06-26 23:57:51 +08:00
<div class="footnotes">
<hr />
<ol>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
<li id="fn:a">This is the note</li>
new tests pass but old tests now fail...
2013-06-26 23:57:51 +08:00
</ol>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
new tests pass but old tests now fail...
2013-06-26 23:57:51 +08:00
</div>
`,
First attempt at supporting Pandoc-style footnotes. The existing tests have not broken but the new functionality does not work yet.
2013-06-25 09:18:47 +08:00
Move footnote prefix to a better place
2014-05-25 03:28:37 +08:00
`testing long[^b] notes.
First attempt at supporting Pandoc-style footnotes. The existing tests have not broken but the new functionality does not work yet.
2013-06-25 09:18:47 +08:00
[^b]: Paragraph 1
Paragraph 2
add target blank attr
2014-03-21 10:52:46 +08:00
First attempt at supporting Pandoc-style footnotes. The existing tests have not broken but the new functionality does not work yet.
2013-06-25 09:18:47 +08:00
` + "```\n\tsome code\n\t```" + `
add target blank attr
2014-03-21 10:52:46 +08:00
First attempt at supporting Pandoc-style footnotes. The existing tests have not broken but the new functionality does not work yet.
2013-06-25 09:18:47 +08:00
Paragraph 3
No longer in the footnote
`,
Move footnote prefix to a better place
2014-05-25 03:28:37 +08:00
`<p>testing long<sup class="footnote-ref" id="fnref:b"><a rel="footnote" href="#fn:b">1</a></sup> notes.</p>
new tests pass but old tests now fail...
2013-06-26 23:57:51 +08:00
<p>No longer in the footnote</p>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
new tests pass but old tests now fail...
2013-06-26 23:57:51 +08:00
<div class="footnotes">
<hr />
<ol>
Implementation and some tests for inline footnotes. Also I noticed the list items had the wrong ids, that was silly of me.
2013-07-01 09:37:52 +08:00
<li id="fn:b"><p>Paragraph 1</p>
new tests pass but old tests now fail...
2013-06-26 23:57:51 +08:00
<p>Paragraph 2</p>
<p><code>
some code
</code></p>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
<p>Paragraph 3</p></li>
new tests pass but old tests now fail...
2013-06-26 23:57:51 +08:00
</ol>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
new tests pass but old tests now fail...
2013-06-26 23:57:51 +08:00
</div>
`,
First attempt at supporting Pandoc-style footnotes. The existing tests have not broken but the new functionality does not work yet.
2013-06-25 09:18:47 +08:00
Move footnote prefix to a better place
2014-05-25 03:28:37 +08:00
`testing[^c] multiple[^d] notes.
First attempt at supporting Pandoc-style footnotes. The existing tests have not broken but the new functionality does not work yet.
2013-06-25 09:18:47 +08:00
new tests pass but old tests now fail...
2013-06-26 23:57:51 +08:00
[^c]: this is [note] c
First attempt at supporting Pandoc-style footnotes. The existing tests have not broken but the new functionality does not work yet.
2013-06-25 09:18:47 +08:00
omg
[^d]: this is note d
what happens here
new tests pass but old tests now fail...
2013-06-26 23:57:51 +08:00
[note]: /link/c
First attempt at supporting Pandoc-style footnotes. The existing tests have not broken but the new functionality does not work yet.
2013-06-25 09:18:47 +08:00
`,
Move footnote prefix to a better place
2014-05-25 03:28:37 +08:00
`<p>testing<sup class="footnote-ref" id="fnref:c"><a rel="footnote" href="#fn:c">1</a></sup> multiple<sup class="footnote-ref" id="fnref:d"><a rel="footnote" href="#fn:d">2</a></sup> notes.</p>
First attempt at supporting Pandoc-style footnotes. The existing tests have not broken but the new functionality does not work yet.
2013-06-25 09:18:47 +08:00
new tests pass but old tests now fail...
2013-06-26 23:57:51 +08:00
<p>omg</p>
<p>what happens here</p>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
new tests pass but old tests now fail...
2013-06-26 23:57:51 +08:00
<div class="footnotes">
<hr />
<ol>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
<li id="fn:c">this is <a href="/link/c">note</a> c</li>
<li id="fn:d">this is note d</li>
Implementation and some tests for inline footnotes. Also I noticed the list items had the wrong ids, that was silly of me.
2013-07-01 09:37:52 +08:00
</ol>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
Implementation and some tests for inline footnotes. Also I noticed the list items had the wrong ids, that was silly of me.
2013-07-01 09:37:52 +08:00
</div>
`,
Move footnote prefix to a better place
2014-05-25 03:28:37 +08:00
"testing inline^[this is the note] notes.\n",
`<p>testing inline<sup class="footnote-ref" id="fnref:this-is-the-note"><a rel="footnote" href="#fn:this-is-the-note">1</a></sup> notes.</p>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
Implementation and some tests for inline footnotes. Also I noticed the list items had the wrong ids, that was silly of me.
2013-07-01 09:37:52 +08:00
<div class="footnotes">
<hr />
<ol>
<li id="fn:this-is-the-note">this is the note</li>
</ol>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
Implementation and some tests for inline footnotes. Also I noticed the list items had the wrong ids, that was silly of me.
2013-07-01 09:37:52 +08:00
</div>
`,
Move footnote prefix to a better place
2014-05-25 03:28:37 +08:00
"testing multiple[^1] types^[inline note] of notes[^2]\n\n[^2]: the second deferred note\n[^1]: the first deferred note\n\n\twhich happens to be a block\n",
`<p>testing multiple<sup class="footnote-ref" id="fnref:1"><a rel="footnote" href="#fn:1">1</a></sup> types<sup class="footnote-ref" id="fnref:inline-note"><a rel="footnote" href="#fn:inline-note">2</a></sup> of notes<sup class="footnote-ref" id="fnref:2"><a rel="footnote" href="#fn:2">3</a></sup></p>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
Implementation and some tests for inline footnotes. Also I noticed the list items had the wrong ids, that was silly of me.
2013-07-01 09:37:52 +08:00
<div class="footnotes">
<hr />
<ol>
<li id="fn:1"><p>the first deferred note</p>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
<p>which happens to be a block</p></li>
Implementation and some tests for inline footnotes. Also I noticed the list items had the wrong ids, that was silly of me.
2013-07-01 09:37:52 +08:00
<li id="fn:inline-note">inline note</li>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
<li id="fn:2">the second deferred note</li>
new tests pass but old tests now fail...
2013-06-26 23:57:51 +08:00
</ol>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
new tests pass but old tests now fail...
2013-06-26 23:57:51 +08:00
</div>
added slice bounds check
2013-07-08 14:54:25 +08:00
`,
Move footnote prefix to a better place
2014-05-25 03:28:37 +08:00
`This is a footnote[^1]^[and this is an inline footnote]
added slice bounds check
2013-07-08 14:54:25 +08:00
[^1]: the footnote text.
may be multiple paragraphs.
`,
Move footnote prefix to a better place
2014-05-25 03:28:37 +08:00
`<p>This is a footnote<sup class="footnote-ref" id="fnref:1"><a rel="footnote" href="#fn:1">1</a></sup><sup class="footnote-ref" id="fnref:and-this-is-an-i"><a rel="footnote" href="#fn:and-this-is-an-i">2</a></sup></p>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
added slice bounds check
2013-07-08 14:54:25 +08:00
<div class="footnotes">
<hr />
<ol>
<li id="fn:1"><p>the footnote text.</p>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
<p>may be multiple paragraphs.</p></li>
added slice bounds check
2013-07-08 14:54:25 +08:00
<li id="fn:and-this-is-an-i">and this is an inline footnote</li>
</ol>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
added slice bounds check
2013-07-08 14:54:25 +08:00
</div>
new tests pass but old tests now fail...
2013-06-26 23:57:51 +08:00
`,
parser no longer returns prematurely from empty footnote ref
2013-07-09 06:34:12 +08:00
Move footnote prefix to a better place
2014-05-25 03:28:37 +08:00
"empty footnote[^]\n\n[^]: fn text",
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
"<p>empty footnote<sup class=\"footnote-ref\" id=\"fnref:\"><a rel=\"footnote\" href=\"#fn:\">1</a></sup></p>\n\n<div class=\"footnotes\">\n\n<hr />\n\n<ol>\n<li id=\"fn:\">fn text</li>\n</ol>\n\n</div>\n",
Fix recognition of consecutive footnotes The second footnote was treated as if the pair of them were a reference style link, without checking if the second bit is another footnote. Fixes issue 158.
2015-04-04 02:05:54 +08:00
"Some text.[^note1]\n\n[^note1]: fn1",
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
"<p>Some text.<sup class=\"footnote-ref\" id=\"fnref:note1\"><a rel=\"footnote\" href=\"#fn:note1\">1</a></sup></p>\n\n<div class=\"footnotes\">\n\n<hr />\n\n<ol>\n<li id=\"fn:note1\">fn1</li>\n</ol>\n\n</div>\n",
Fix recognition of consecutive footnotes The second footnote was treated as if the pair of them were a reference style link, without checking if the second bit is another footnote. Fixes issue 158.
2015-04-04 02:05:54 +08:00
"Some text.[^note1][^note2]\n\n[^note1]: fn1\n[^note2]: fn2\n",
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
"<p>Some text.<sup class=\"footnote-ref\" id=\"fnref:note1\"><a rel=\"footnote\" href=\"#fn:note1\">1</a></sup><sup class=\"footnote-ref\" id=\"fnref:note2\"><a rel=\"footnote\" href=\"#fn:note2\">2</a></sup></p>\n\n<div class=\"footnotes\">\n\n<hr />\n\n<ol>\n<li id=\"fn:note1\">fn1</li>\n\n<li id=\"fn:note2\">fn2</li>\n</ol>\n\n</div>\n",
Fix footnote followed by a reference style link When parsing a deferred footnote, we already know it's a footnote from the '[^' part, so we can use that to hit a proper switch branch (default) a bit later on. Closes #164.
2015-10-13 02:18:33 +08:00
`Bla bla [^1] [WWW][w3]
[^1]: This is a footnote
[w3]: http://www.w3.org/
`,
`<p>Bla bla <sup class="footnote-ref" id="fnref:1"><a rel="footnote" href="#fn:1">1</a></sup> <a href="http://www.w3.org/">WWW</a></p>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
Fix footnote followed by a reference style link When parsing a deferred footnote, we already know it's a footnote from the '[^' part, so we can use that to hit a proper switch branch (default) a bit later on. Closes #164.
2015-10-13 02:18:33 +08:00
<div class="footnotes">
<hr />
<ol>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
<li id="fn:1">This is a footnote</li>
Fix footnote followed by a reference style link When parsing a deferred footnote, we already know it's a footnote from the '[^' part, so we can use that to hit a proper switch branch (default) a bit later on. Closes #164.
2015-10-13 02:18:33 +08:00
</ol>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
Fix footnote followed by a reference style link When parsing a deferred footnote, we already know it's a footnote from the '[^' part, so we can use that to hit a proper switch branch (default) a bit later on. Closes #164.
2015-10-13 02:18:33 +08:00
</div>
Fix footnote following an exclamation point Link parser interpreted the sequence "![^foo]" as an image, but if footnote extension is enabled, it's quite clear that it should be interpreted as a footnote following something with an exclamation point at the end. Closes #194.
2015-11-04 02:52:36 +08:00
`,
`This is exciting![^fn1]
[^fn1]: Fine print
`,
`<p>This is exciting!<sup class="footnote-ref" id="fnref:fn1"><a rel="footnote" href="#fn:fn1">1</a></sup></p>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
Fix footnote following an exclamation point Link parser interpreted the sequence "![^foo]" as an image, but if footnote extension is enabled, it's quite clear that it should be interpreted as a footnote following something with an exclamation point at the end. Closes #194.
2015-11-04 02:52:36 +08:00
<div class="footnotes">
<hr />
<ol>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
<li id="fn:fn1">Fine print</li>
Fix footnote following an exclamation point Link parser interpreted the sequence "![^foo]" as an image, but if footnote extension is enabled, it's quite clear that it should be interpreted as a footnote following something with an exclamation point at the end. Closes #194.
2015-11-04 02:52:36 +08:00
</ol>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
Fix footnote following an exclamation point Link parser interpreted the sequence "![^foo]" as an image, but if footnote extension is enabled, it's quite clear that it should be interpreted as a footnote following something with an exclamation point at the end. Closes #194.
2015-11-04 02:52:36 +08:00
</div>
Fix footnote followed by a reference style link When parsing a deferred footnote, we already know it's a footnote from the '[^' part, so we can use that to hit a proper switch branch (default) a bit later on. Closes #164.
2015-10-13 02:18:33 +08:00
`,
Move footnote rendering to the renderer Clean up footnotes part of an AST: don't force HTML-specific pieces there, just keep a clean list of footnotes. Since some renderers might want to process footnotes differently, let them know about footnotes by having a flag on that list.
2016-09-03 17:39:16 +08:00
`This text does not reference a footnote.
[^footnote]: But it has a footnote! And it gets omitted.
`,
"<p>This text does not reference a footnote.</p>\n",
Move footnote prefix to a better place
2014-05-25 03:28:37 +08:00
}
func TestFootnotes(t *testing.T) {
Wrap inline test parameters in a struct Take advantage of zero value initialization.
2016-04-04 16:18:50 +08:00
doTestsInlineParam(t, footnoteTests, TestParams{
Change the public interface to use functional options Convert the most important Blackfriday's function, Markdown(), to accept functional options (as per this Dave Cheney's post: https://dave.cheney.net/2014/10/17/functional-options-for-friendly-apis)
2017-02-02 15:35:10 +08:00
extensions: Footnotes,
Wrap inline test parameters in a struct Take advantage of zero value initialization.
2016-04-04 16:18:50 +08:00
})
Move footnote prefix to a better place
2014-05-25 03:28:37 +08:00
}
func TestFootnotesWithParameters(t *testing.T) {
tests := make([]string, len(footnoteTests))
prefix := "testPrefix"
Add tests for new footnote functionality
2014-05-26 02:07:05 +08:00
returnText := "ret"
re := regexp.MustCompile(`(?ms)<li id="fn:(\S+?)">(.*?)</li>`)
// Transform the test expectations to match the parameters we're using.
Move footnote prefix to a better place
2014-05-25 03:28:37 +08:00
for i, test := range footnoteTests {
Add tests for new footnote functionality
2014-05-26 02:07:05 +08:00
if i%2 == 1 {
test = strings.Replace(test, "fn:", "fn:"+prefix, -1)
test = strings.Replace(test, "fnref:", "fnref:"+prefix, -1)
test = re.ReplaceAllString(test, `<li id="fn:$1">$2 <a class="footnote-return" href="#fnref:$1">ret</a></li>`)
}
tests[i] = test
}
Move footnote prefix to a better place
2014-05-25 03:28:37 +08:00
Go style: more Html -> HTML renames
2016-04-01 20:37:21 +08:00
params := HTMLRendererParameters{
Add tests for new footnote functionality
2014-05-26 02:07:05 +08:00
FootnoteAnchorPrefix: prefix,
FootnoteReturnLinkContents: returnText,
First attempt at supporting Pandoc-style footnotes. The existing tests have not broken but the new functionality does not work yet.
2013-06-25 09:18:47 +08:00
}
Wrap inline test parameters in a struct Take advantage of zero value initialization.
2016-04-04 16:18:50 +08:00
doTestsInlineParam(t, tests, TestParams{
Change the public interface to use functional options Convert the most important Blackfriday's function, Markdown(), to accept functional options (as per this Dave Cheney's post: https://dave.cheney.net/2014/10/17/functional-options-for-friendly-apis)
2017-02-02 15:35:10 +08:00
extensions: Footnotes,
Wrap inline test parameters in a struct Take advantage of zero value initialization.
2016-04-04 16:18:50 +08:00
HTMLFlags: FootnoteReturnLinks,
HTMLRendererParameters: params,
})
First attempt at supporting Pandoc-style footnotes. The existing tests have not broken but the new functionality does not work yet.
2013-06-25 09:18:47 +08:00
}
Add support for angled, double quotes The flag `HTML_SMARTYPANTS_ANGLED_QUOTES` combined with `HTML_USE_SMARTYPANTS` configures rendering of double quotes as angled left and right quotes (&laquo; &raquo;). The SmartyPants documentation mentions a special syntax for these, `<<>>`, a syntax neither pretty nor user friendly. Typical use cases would be either or, or combined, but never in the same document. As an example would be a person from Norway; he has a blog in both English and Norwegian (his native tounge); he would then configure Blackfriday to use angled quotes for the Norwegian section, but keep them as reqular double quotes for the English. If the flag `HTML_SMARTYPANTS_ANGLED_QUOTES` is not provided, everything works as before this commit.
2014-11-06 06:18:32 +08:00
Fix nested footnotes This is both nasty and neat at the same time. All the code could handle nested footnotes just fine, the only place that was not working was the final loop that printed the list. The loop was in a range form, which couldn't account for another footnote being inserted while processing existing ones. Changing the loop to the iterative form solves that. Closes #193.
2015-11-03 02:17:46 +08:00
func TestNestedFootnotes(t *testing.T) {
var tests = []string{
`Paragraph.[^fn1]
[^fn1]:
Asterisk[^fn2]
[^fn2]:
Obelisk`,
`<p>Paragraph.<sup class="footnote-ref" id="fnref:fn1"><a rel="footnote" href="#fn:fn1">1</a></sup></p>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
Fix nested footnotes This is both nasty and neat at the same time. All the code could handle nested footnotes just fine, the only place that was not working was the final loop that printed the list. The loop was in a range form, which couldn't account for another footnote being inserted while processing existing ones. Changing the loop to the iterative form solves that. Closes #193.
2015-11-03 02:17:46 +08:00
<div class="footnotes">
<hr />
<ol>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
<li id="fn:fn1">Asterisk<sup class="footnote-ref" id="fnref:fn2"><a rel="footnote" href="#fn:fn2">2</a></sup></li>
<li id="fn:fn2">Obelisk</li>
Fix nested footnotes This is both nasty and neat at the same time. All the code could handle nested footnotes just fine, the only place that was not working was the final loop that printed the list. The loop was in a range form, which couldn't account for another footnote being inserted while processing existing ones. Changing the loop to the iterative form solves that. Closes #193.
2015-11-03 02:17:46 +08:00
</ol>
Fix footnote tests This commit does some changes to the test suite. The changes are only to the newlines. Turns out the former implementation of footnotes produced slightly different spacing when rendering the footnotes list. The new implementation produces the list that is compatible with the rest of the package.
2016-03-30 20:03:11 +08:00
Fix nested footnotes This is both nasty and neat at the same time. All the code could handle nested footnotes just fine, the only place that was not working was the final loop that printed the list. The loop was in a range form, which couldn't account for another footnote being inserted while processing existing ones. Changing the loop to the iterative form solves that. Closes #193.
2015-11-03 02:17:46 +08:00
</div>
`,
}
Change the public interface to use functional options Convert the most important Blackfriday's function, Markdown(), to accept functional options (as per this Dave Cheney's post: https://dave.cheney.net/2014/10/17/functional-options-for-friendly-apis)
2017-02-02 15:35:10 +08:00
doTestsInlineParam(t, tests, TestParams{extensions: Footnotes})
Fix nested footnotes This is both nasty and neat at the same time. All the code could handle nested footnotes just fine, the only place that was not working was the final loop that printed the list. The loop was in a range form, which couldn't account for another footnote being inserted while processing existing ones. Changing the loop to the iterative form solves that. Closes #193.
2015-11-03 02:17:46 +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 TestInlineComments(t *testing.T) {
var tests = []string{
"Hello <!-- there ->\n",
"<p>Hello &lt;!&mdash; there &ndash;&gt;</p>\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
"Hello <!-- there -->\n",
"<p>Hello <!-- there --></p>\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
"Hello <!-- there -->",
"<p>Hello <!-- there --></p>\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
"Hello <!---->\n",
"<p>Hello <!----></p>\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
"Hello <!-- there -->\na",
"<p>Hello <!-- there -->\na</p>\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
"* list <!-- item -->\n",
"<ul>\n<li>list <!-- item --></li>\n</ul>\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
"<!-- Front --> comment\n",
"<p><!-- Front --> comment</p>\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
"blahblah\n<!--- foo -->\nrhubarb\n",
"<p>blahblah\n<!--- foo -->\nrhubarb</p>\n",
}
Factor Smartypants to HTML Smartypants is HTML-specific. There is no need to run Smartypants from `Render()`. This simplifies extensions built upon the HTML renderer.
2016-08-10 12:26:37 +08:00
doTestsInlineParam(t, tests, TestParams{HTMLFlags: Smartypants | SmartypantsDashes})
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 support for angled, double quotes The flag `HTML_SMARTYPANTS_ANGLED_QUOTES` combined with `HTML_USE_SMARTYPANTS` configures rendering of double quotes as angled left and right quotes (&laquo; &raquo;). The SmartyPants documentation mentions a special syntax for these, `<<>>`, a syntax neither pretty nor user friendly. Typical use cases would be either or, or combined, but never in the same document. As an example would be a person from Norway; he has a blog in both English and Norwegian (his native tounge); he would then configure Blackfriday to use angled quotes for the Norwegian section, but keep them as reqular double quotes for the English. If the flag `HTML_SMARTYPANTS_ANGLED_QUOTES` is not provided, everything works as before this commit.
2014-11-06 06:18:32 +08:00
func TestSmartDoubleQuotes(t *testing.T) {
var tests = []string{
"this should be normal \"quoted\" text.\n",
"<p>this should be normal &ldquo;quoted&rdquo; text.</p>\n",
"this \" single double\n",
"<p>this &ldquo; single double</p>\n",
"two pair of \"some\" quoted \"text\".\n",
"<p>two pair of &ldquo;some&rdquo; quoted &ldquo;text&rdquo;.</p>\n"}
Factor Smartypants to HTML Smartypants is HTML-specific. There is no need to run Smartypants from `Render()`. This simplifies extensions built upon the HTML renderer.
2016-08-10 12:26:37 +08:00
doTestsInlineParam(t, tests, TestParams{HTMLFlags: Smartypants})
Add support for angled, double quotes The flag `HTML_SMARTYPANTS_ANGLED_QUOTES` combined with `HTML_USE_SMARTYPANTS` configures rendering of double quotes as angled left and right quotes (&laquo; &raquo;). The SmartyPants documentation mentions a special syntax for these, `<<>>`, a syntax neither pretty nor user friendly. Typical use cases would be either or, or combined, but never in the same document. As an example would be a person from Norway; he has a blog in both English and Norwegian (his native tounge); he would then configure Blackfriday to use angled quotes for the Norwegian section, but keep them as reqular double quotes for the English. If the flag `HTML_SMARTYPANTS_ANGLED_QUOTES` is not provided, everything works as before this commit.
2014-11-06 06:18:32 +08:00
}
Add Smartypants support for French Guillemets This is a port of the fix for #378 in v1. Fixes #380
2017-07-31 23:40:36 +08:00
func TestSmartDoubleQuotesNBSP(t *testing.T) {
var tests = []string{
"this should be normal \"quoted\" text.\n",
"<p>this should be normal &ldquo;&nbsp;quoted&nbsp;&rdquo; text.</p>\n",
"this \" single double\n",
"<p>this &ldquo;&nbsp; single double</p>\n",
"two pair of \"some\" quoted \"text\".\n",
"<p>two pair of &ldquo;&nbsp;some&nbsp;&rdquo; quoted &ldquo;&nbsp;text&nbsp;&rdquo;.</p>\n"}
doTestsInlineParam(t, tests, TestParams{HTMLFlags: Smartypants | SmartypantsQuotesNBSP})
}
Add support for angled, double quotes The flag `HTML_SMARTYPANTS_ANGLED_QUOTES` combined with `HTML_USE_SMARTYPANTS` configures rendering of double quotes as angled left and right quotes (&laquo; &raquo;). The SmartyPants documentation mentions a special syntax for these, `<<>>`, a syntax neither pretty nor user friendly. Typical use cases would be either or, or combined, but never in the same document. As an example would be a person from Norway; he has a blog in both English and Norwegian (his native tounge); he would then configure Blackfriday to use angled quotes for the Norwegian section, but keep them as reqular double quotes for the English. If the flag `HTML_SMARTYPANTS_ANGLED_QUOTES` is not provided, everything works as before this commit.
2014-11-06 06:18:32 +08:00
func TestSmartAngledDoubleQuotes(t *testing.T) {
var tests = []string{
"this should be angled \"quoted\" text.\n",
"<p>this should be angled &laquo;quoted&raquo; text.</p>\n",
"this \" single double\n",
"<p>this &laquo; single double</p>\n",
"two pair of \"some\" quoted \"text\".\n",
"<p>two pair of &laquo;some&raquo; quoted &laquo;text&raquo;.</p>\n"}
Factor Smartypants to HTML Smartypants is HTML-specific. There is no need to run Smartypants from `Render()`. This simplifies extensions built upon the HTML renderer.
2016-08-10 12:26:37 +08:00
doTestsInlineParam(t, tests, TestParams{HTMLFlags: Smartypants | SmartypantsAngledQuotes})
Add support for angled, double quotes The flag `HTML_SMARTYPANTS_ANGLED_QUOTES` combined with `HTML_USE_SMARTYPANTS` configures rendering of double quotes as angled left and right quotes (&laquo; &raquo;). The SmartyPants documentation mentions a special syntax for these, `<<>>`, a syntax neither pretty nor user friendly. Typical use cases would be either or, or combined, but never in the same document. As an example would be a person from Norway; he has a blog in both English and Norwegian (his native tounge); he would then configure Blackfriday to use angled quotes for the Norwegian section, but keep them as reqular double quotes for the English. If the flag `HTML_SMARTYPANTS_ANGLED_QUOTES` is not provided, everything works as before this commit.
2014-11-06 06:18:32 +08:00
}
Avoid converting dates into fractions So that dates like 1/2/2005 and 2005/3/4 stay the way it is without turning into ½/2005 and 2005/¾. See http://discuss.gohugo.io/t/any-way-to-disable-smart-fractions/328 for discussions.
2015-01-25 06:23:48 +08:00
Add Smartypants support for French Guillemets This is a port of the fix for #378 in v1. Fixes #380
2017-07-31 23:40:36 +08:00
func TestSmartAngledDoubleQuotesNBSP(t *testing.T) {
var tests = []string{
"this should be angled \"quoted\" text.\n",
"<p>this should be angled &laquo;&nbsp;quoted&nbsp;&raquo; text.</p>\n",
"this \" single double\n",
"<p>this &laquo;&nbsp; single double</p>\n",
"two pair of \"some\" quoted \"text\".\n",
"<p>two pair of &laquo;&nbsp;some&nbsp;&raquo; quoted &laquo;&nbsp;text&nbsp;&raquo;.</p>\n"}
doTestsInlineParam(t, tests, TestParams{HTMLFlags: Smartypants | SmartypantsAngledQuotes | SmartypantsQuotesNBSP})
}
Avoid converting dates into fractions So that dates like 1/2/2005 and 2005/3/4 stay the way it is without turning into ½/2005 and 2005/¾. See http://discuss.gohugo.io/t/any-way-to-disable-smart-fractions/328 for discussions.
2015-01-25 06:23:48 +08:00
func TestSmartFractions(t *testing.T) {
var tests = []string{
"1/2, 1/4 and 3/4; 1/4th and 3/4ths\n",
"<p>&frac12;, &frac14; and &frac34;; &frac14;th and &frac34;ths</p>\n",
"1/2/2015, 1/4/2015, 3/4/2015; 2015/1/2, 2015/1/4, 2015/3/4.\n",
"<p>1/2/2015, 1/4/2015, 3/4/2015; 2015/1/2, 2015/1/4, 2015/3/4.</p>\n"}
Factor Smartypants to HTML Smartypants is HTML-specific. There is no need to run Smartypants from `Render()`. This simplifies extensions built upon the HTML renderer.
2016-08-10 12:26:37 +08:00
doTestsInlineParam(t, tests, TestParams{HTMLFlags: Smartypants})
Avoid converting dates into fractions So that dates like 1/2/2005 and 2005/3/4 stay the way it is without turning into ½/2005 and 2005/¾. See http://discuss.gohugo.io/t/any-way-to-disable-smart-fractions/328 for discussions.
2015-01-25 06:23:48 +08:00
tests = []string{
"1/2, 2/3, 81/100 and 1000000/1048576.\n",
"<p><sup>1</sup>&frasl;<sub>2</sub>, <sup>2</sup>&frasl;<sub>3</sub>, <sup>81</sup>&frasl;<sub>100</sub> and <sup>1000000</sup>&frasl;<sub>1048576</sub>.</p>\n",
"1/2/2015, 1/4/2015, 3/4/2015; 2015/1/2, 2015/1/4, 2015/3/4.\n",
"<p>1/2/2015, 1/4/2015, 3/4/2015; 2015/1/2, 2015/1/4, 2015/3/4.</p>\n"}
Factor Smartypants to HTML Smartypants is HTML-specific. There is no need to run Smartypants from `Render()`. This simplifies extensions built upon the HTML renderer.
2016-08-10 12:26:37 +08:00
doTestsInlineParam(t, tests, TestParams{HTMLFlags: Smartypants | SmartypantsFractions})
Avoid converting dates into fractions So that dates like 1/2/2005 and 2005/3/4 stay the way it is without turning into ½/2005 and 2005/¾. See http://discuss.gohugo.io/t/any-way-to-disable-smart-fractions/328 for discussions.
2015-01-25 06:23:48 +08:00
}
Fix broken test and add test for HTML_SMARTYPANTS_DASHES
2015-10-28 02:21:08 +08:00
func TestDisableSmartDashes(t *testing.T) {
doTestsInlineParam(t, []string{
"foo - bar\n",
"<p>foo - bar</p>\n",
"foo -- bar\n",
"<p>foo -- bar</p>\n",
"foo --- bar\n",
"<p>foo --- bar</p>\n",
Wrap inline test parameters in a struct Take advantage of zero value initialization.
2016-04-04 16:18:50 +08:00
}, TestParams{})
Fix broken test and add test for HTML_SMARTYPANTS_DASHES
2015-10-28 02:21:08 +08:00
doTestsInlineParam(t, []string{
"foo - bar\n",
"<p>foo &ndash; bar</p>\n",
"foo -- bar\n",
"<p>foo &mdash; bar</p>\n",
"foo --- bar\n",
"<p>foo &mdash;&ndash; bar</p>\n",
Factor Smartypants to HTML Smartypants is HTML-specific. There is no need to run Smartypants from `Render()`. This simplifies extensions built upon the HTML renderer.
2016-08-10 12:26:37 +08:00
}, TestParams{HTMLFlags: Smartypants | SmartypantsDashes})
Fix broken test and add test for HTML_SMARTYPANTS_DASHES
2015-10-28 02:21:08 +08:00
doTestsInlineParam(t, []string{
"foo - bar\n",
"<p>foo - bar</p>\n",
"foo -- bar\n",
"<p>foo &ndash; bar</p>\n",
"foo --- bar\n",
"<p>foo &mdash; bar</p>\n",
Factor Smartypants to HTML Smartypants is HTML-specific. There is no need to run Smartypants from `Render()`. This simplifies extensions built upon the HTML renderer.
2016-08-10 12:26:37 +08:00
}, TestParams{HTMLFlags: Smartypants | SmartypantsLatexDashes | SmartypantsDashes})
Fix broken test and add test for HTML_SMARTYPANTS_DASHES
2015-10-28 02:21:08 +08:00
doTestsInlineParam(t, []string{
"foo - bar\n",
"<p>foo - bar</p>\n",
"foo -- bar\n",
"<p>foo -- bar</p>\n",
"foo --- bar\n",
"<p>foo --- bar</p>\n",
Factor Smartypants to HTML Smartypants is HTML-specific. There is no need to run Smartypants from `Render()`. This simplifies extensions built upon the HTML renderer.
2016-08-10 12:26:37 +08:00
}, TestParams{HTMLFlags: Smartypants | SmartypantsLatexDashes})
Implement SkipLinks, add test
2016-04-04 19:08:35 +08:00
}
func TestSkipLinks(t *testing.T) {
doTestsInlineParam(t, []string{
"[foo](gopher://foo.bar)",
"<p><tt>foo</tt></p>\n",
"[foo](mailto://bar/)\n",
"<p><tt>foo</tt></p>\n",
}, TestParams{
HTMLFlags: SkipLinks,
})
Fix broken test and add test for HTML_SMARTYPANTS_DASHES
2015-10-28 02:21:08 +08:00
}
Add test for UseXHTML
2016-04-05 14:51:46 +08:00
Implement SkipImages and add test
2016-04-05 16:12:30 +08:00
func TestSkipImages(t *testing.T) {
doTestsInlineParam(t, []string{
"![foo](/bar/)\n",
"<p></p>\n",
}, TestParams{
HTMLFlags: SkipImages,
})
}
Add test for UseXHTML
2016-04-05 14:51:46 +08:00
func TestUseXHTML(t *testing.T) {
doTestsParam(t, []string{
"---",
"<hr>\n",
}, TestParams{})
doTestsParam(t, []string{
"---",
"<hr />\n",
}, TestParams{HTMLFlags: UseXHTML})
}
Implement SkipHTML, add test
2016-04-05 17:37:02 +08:00
func TestSkipHTML(t *testing.T) {
doTestsParam(t, []string{
"<div class=\"foo\"></div>\n\ntext\n\n<form>the form</form>",
Get rid of the preprocess stage Yay!!
2016-11-11 03:49:58 +08:00
"<p>text</p>\n\n<p>the form</p>\n",
Implement SkipHTML, add test
2016-04-05 17:37:02 +08:00
"text <em>inline html</em> more text",
"<p>text inline html more text</p>\n",
}, TestParams{HTMLFlags: SkipHTML})
}
Add Smartypants support for French Guillemets This is a port of the fix for #378 in v1. Fixes #380
2017-07-31 23:40:36 +08:00
func BenchmarkSmartDoubleQuotes(b *testing.B) {
params := TestParams{HTMLFlags: Smartypants}
params.extensions |= Autolink | Strikethrough
params.HTMLFlags |= UseXHTML
for i := 0; i < b.N; i++ {
runMarkdown("this should be normal \"quoted\" text.\n", params)
}
}
Reference in New Issue Copy Permalink