aboutsummaryrefslogtreecommitdiffstats
path: root/tests/extensions
Commit message (Collapse)AuthorAgeFilesLines
* Issue #368: Fix Markdown in raw HTML stops workingfacelessuser2014-11-192-3/+24
| | | | | | | Originally there was an infinite loop issue that was patched in issue #308. Unfortunately, it was fixed all the way. This fix patches the infinite loop fix to only add an offset to the `right_listindex` when it is in a infinite loop scenario.
* Code Blocks must always be AtomicStringsWaylan Limberg2014-09-082-2/+11
| | | | | | | | | | | | | | | | | | Fixes #340. The "inline" TreeProcessor runs before the "prettify" TreeProcessor, but the "smarty" TreeProcessor (wich is just another instance of `InlineProcessor`) runs after the "prettify" TreeProcessor. The problem was that the "prettify" TreeProcessor was losing the AtomicString quality of the text of code blocks (any operation on a string creates a new string. When that string is an AtomicString, the new string must explicitly be declared as an AtomicString. As the "prettify" TreeProcessor cleans up newlines on code blocks, it was changing the AtomicString to a normal string. And as `InlineProcessor` identifies what elements to skip solely by whether the text is an AtomicString, the "smarty" instance was running on code blocks. Importantly, I added a test of code blocks and spans for smarty, so this shouldn't break again.
* More updates to test configs.Waylan Limberg2014-08-293-0/+22
| | | | | | | | | | | | | | The last few extensions were updated to accept dicts/**kwargs as configs and more tests were updated. Also updated extra to actually accept configs. Note that extra requires an extra level of dicts. First you need to indicate tha the settings are for extra, then, which extension extra wraps. I'm not crazy abount this, bit not sur ehow else to do it without making all the configs a global attribute on the Markdown class to that any extention can access any other extensions config settings. I don't think we wnat to do that. Also updated extra to use dot notation for the sub-extensions.
* All extension tests now use python dot notation.Waylan Limberg2014-08-292-28/+28
| | | | | | | | | | All named extensions now use python dot notation in the tests - including all builtin extensions (eg: 'extra' => 'markdown.extensions.extra'). This is in anticipation of #336. Note there are a few tests (in the error tests) that will still need updating, but not till we make the change as they will test for the new error message.
* Refactored test framework to use YAML config files rather than INI. Fixes #333.Waylan Limberg2014-08-202-44/+78
|
* Fixed an old typo in the smarty extension and added a test case.Martin Altmayer2014-08-112-1/+3
|
* 100% test coverage of admonitionsWaylan Limberg2014-07-102-0/+2
|
* smarty: add support for angled quotesDmitry Shachnev2014-06-193-1/+6
| | | | See <http://en.wikipedia.org/wiki/Guillemet>.
* Add failing unit test for smarty: ellipsis before close double quote ↵Lawrence Kesteloot2014-05-312-0/+3
| | | | generates opening double quote.
* Merge pull request #311 from mitya57/masterWaylan Limberg2014-05-261-1/+1
|\ | | | | Make smarty extension work together with attr_list
| * Add smarty to extensions for attr_list testDmitry Shachnev2014-05-061-1/+1
| | | | | | | | To make it easier to notice (and fix) the failure.
* | Fix issue308 and fix (unrelated) failure to break out of nest loop.ryneeverett2014-05-212-1/+14
|/
* Add a (failing) test for Smarty extension.Dmitry Shachnev2014-02-132-1/+3
|
* Fix some tests failuresDmitry Shachnev2014-02-121-1/+1
|
* tables_and_attr_list testryneeverett2014-01-113-0/+25
|
* Issue #52ryneeverett2013-10-142-6/+57
|
* toc: insert `&para;` instead of raw unicode characterDmitry Shachnev2013-09-291-4/+4
|
* Add tests for the previous two commitsDmitry Shachnev2013-09-253-10/+10
|
* Ensure each term on def list maintains its own loose status.Waylan Limberg2013-09-022-1/+22
| | | | | | Previously, the code was ignoring whether this was a new term when determining whether the currect item should be loose or not. Fixes #243. Thanks for the report @Anomareh.
* Some fixes requested by @waylan, cleanup and tests improvementsDmitry Shachnev2013-07-272-2/+11
|
* Add smarty extension, based on SmartyPants libraryDmitry Shachnev2013-07-263-0/+38
|
* Added support for attr_lists on definition list terms.Waylan Limberg2013-07-193-2/+22
| | | | | | | | Like headers (h1-6) dt's can only be on one line, so we need to use the header regex on dt's. This was implemented after considering a recent [discussion](http://six.pairlist.net/pipermail/markdown-discuss/2013-July/002859.html) on the markdown mailing list. Prior to that discussion, I never considered that it was impossable to set block level attrs on dt's. Now it is.
* Allow inline attr_lists at end of header.Waylan Limberg2013-07-192-2/+2
| | | | | | | | | | A header can be only one line - so unlike other block level elements, a attr_list must be at th eend of the line. To disingush it from an inline attr_list on the last child in a header, we must require at least one space before th eblock-level attrt_list. Always intended it to work that way. Not sure how I missed that before. At least we're testing for it now.
* Attr_List Extension now also supports nested ol's.Waylan Limberg2013-07-192-1/+43
| | | | | | | | | | Not sure how I missed that when committing ea4af0d. Also as a side-effect, this fixes #230 - which brought my previous oversight to my attention. Thanks for the report @divisoryang. Also added some tests - including tests of list items without attr_lists. Sometimes I forget to test markup that does not use an extension when an extension is enabled. That's what resulted in #230 being reported.
* Attr_List Extension now support attr_lists on nested lists.Waylan Limberg2013-06-162-1/+23
| | | | | | A list item with a nested list complicates were the attr_list can be. Fixes #218. Thanks for the report @jpzimmer.
* Updated toc tests.Waylan Limberg2013-02-192-2/+2
|
* adding test for out of order headlinesbenjaoming2013-02-183-0/+16
|
* Allow capitalized Admonition title.Waylan Limberg2013-02-121-1/+1
| | | | | If an adminition title is capitalized, the html class on the div should still be lowercased.
* Merge branch 'master' into admonitionTiago Serafim2013-02-097-1/+49
|\ | | | | | | | | | | Conflicts: docs/extensions/index.txt tests/extensions/test.cfg
| * nl2br and attr_list compatability.Waylan Limberg2013-02-063-0/+6
| | | | | | | | | | | | Fixes #177. When using both extensions, breaks (`<br>`) must have a linebreak (`\n`) after them before attr_list is run. This patch reorders the treeprocessors so that happens ('attr_list' runs after 'prettify' not before). Also had to alter headerid extension so it runs after 'prettify' or it would run before 'attr_list' if loaded before 'attr_list' by user.
| * Account for a paragraph that starts with a colon when processing def_listsWaylan Limberg2013-02-062-0/+40
| | | | | | | | Fixes #171. While that report provided an example of an unordered list item that started with a colon, any block that starts with a colon and has no siblings before it (paragraph as begining if document, list item, etc) all exhibit this same behavior. Following PHP Markdown Extra's lead, these are not definition items as they have no term before them.
| * Fixed #164. attr_list extension attribute names are now sanitized and won't ↵Waylan Limberg2012-12-132-1/+3
| | | | | | | | crash the serealizer.
* | More tests for the extension and new tests for the RE. It's now possible to ↵Tiago Serafim2012-09-192-0/+22
| | | | | | | | use an explicit blank title to not have the <p> tag with the title rendered.
* | Initial version with insufficient tests and no docs.Tiago Serafim2012-09-023-0/+39
|/
* Fix `footnote_many_footnotes` test as per #129Dmitry Shachnev2012-08-251-2398/+2398
|
* Fixed #129. Footnotes now output valid HTML5.Waylan Limberg2012-08-093-15/+15
| | | | | | | | | | | | | | | | As HTML5 has depreciated use of `rev=anything` and `rel=footnotes`, they are no longer inlcuded in the output when the output_format is set to HTML5. Note that if someone successful registers a spec for `rel=footnotes` in the future (as a microformat), then that could be considered valid. But until that happens, it is invlaid to use in HTML5. Therefore, we remove it from the output (when outputing HTML% only). As an alternative, two new classes are set (in all output_formats). On the link to the footnote (where `rel=footnotes` was used), we set `class=footnote-ref` and on the backlink (where `rev=footnote` was used), we set `class=footnote-backref`. Also updated the tests to reflect to the new classes in the output.
* Added support for <foo>+<bar> lexers of Pygmentspapaeye2012-07-212-0/+20
|
* Fixes #64. Added sane_list extension.Waylan Limberg2012-01-243-0/+40
| | | | | | | | | | This is an extension which alters the behavior of lists to be less surprising. If turned out to be rather simple to code. I'm surprised no one had written it yet. I should note that this extension does not generate separate lists if different unordered list markers are used (`*` verses `-` verses `+`) The way the parser works that would be a little more tricky.
* Removed Codehilite from tests.Waylan Limberg2012-01-202-32/+32
| | | | | | Codehilite generates differant output with differant versiosn of pygments. We support those various versions of pygments but can't unsure that the same version is always available on every platform tests are run on.
* Support github-flavored markdown by making the '.' optional before language ↵Mike Dirolf2012-01-173-0/+69
| | | | type.
* Fenced code blocks need to end with a fence on its own line.Mike Dirolf2012-01-173-0/+69
|
* also undo changes to the test.cfgDaniel Gottlieb2011-12-271-4/+0
|
* appropriately move the tests to the fenced code documentation in the ↵Daniel Gottlieb2011-12-272-150/+0
| | | | extension source
* Allow tildes or backticks in the fenced_code extension to support the syntax ↵Daniel Gottlieb2011-12-273-1/+155
| | | | used by github
* Some more tests for issue #51. An upate to Marcin Kasperski's tests (which I ↵Waylan Limberg2011-11-173-2402/+1212
| | | | previously merged). Thanks Marcin. Also added a test for not-indented secondary lines of a first paragraph in a footnote definition.
* Merge git://github.com/Mekk/Python-Markdown into mekkWaylan Limberg2011-11-172-0/+10796
|\
| * Example test for #51 (crash on docs with +1000 footnotes)Marcin Kasperski2011-11-102-0/+10796
| |
* | Fixed #51. Removed recussion from footnote preproccessor. Also refactors the ↵Waylan Limberg2011-11-183-14/+7
|/ | | | code to provide a few other minor improvements s that output more closely matches php's output. Thus the changes in the tests.
* Fixed #30. Tables now allow three spaces of indent like PHP Markdown Extra. ↵Waylan Limberg2011-06-292-1/+62
| | | | Thanks to skurfer for report and inital patch.
* Added docs and tests to attr_list ext. Closes #7.Waylan Limberg2011-06-203-0/+55
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-02 11:54:43 +0000