aboutsummaryrefslogtreecommitdiffstats
path: root/tests/gfm_table.rs (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Fix GFM tables to require a non-pipe in header rowLibravatar Titus Wormer2022-10-281-0/+18
| | | | Related-to: GH-20.
* Refactor to use default trait in testsLibravatar Titus Wormer2022-10-141-107/+77
|
* Remove some unused code in gfm tablesLibravatar Titus Wormer2022-10-131-0/+19
|
* Rename crate to `markdown`Libravatar Titus Wormer2022-10-131-67/+67
|
* Refactor to use a bunch of `into`Libravatar Titus Wormer2022-10-111-11/+11
|
* Refactor to split parse from compile optionsLibravatar Titus Wormer2022-10-061-30/+72
|
* Add support for turning mdast to hastLibravatar Titus Wormer2022-09-281-2/+4
|
* Add support for compiling to mdastLibravatar Titus Wormer2022-09-261-1/+131
| | | | See: <https://github.com/syntax-tree/mdast>.
* Add support for parsing MDX ESM, expressionsLibravatar Titus Wormer2022-09-191-2/+4
| | | | | | | | | | | | | | | | This commit adds support for hooks that lets a user integrate another parser with `micromark-rs`, to parse ESM and expressions according to a particular grammar (such as a programming language, typically JavaScript). For an example integrating with SWC, see `tests/test_utils/mod.rs`. The integration occurs with two functions passed in `options`: `mdx_expression_parse` and `mdx_esm_parse`. The can signal back to micromark when they are successful, whether there is an error at the end (in which case micromark will try to parse more), or whether there is a syntax error (in which case micromark will crash).
* Fix to prefer flow over definitions, setext headingsLibravatar Titus Wormer2022-09-141-0/+6
| | | | | | | | | | | | | | An undocumented part of CommonMark is how to deal with things in definition labels or definition titles (which both can span multiple lines). Can flow (or containers?) interrupt them? They can according to the `cmark` reference parser, so this was implemented here. This adds a new `Content` content type, which houses zero or more definitions, and then zero-or-one paragraphs. Content can be followed by a setext heading underline, which either turns into a setext heading when the content ends in a paragraph, or turns into the start of the following paragraph when it is followed by content that starts with a paragraph, or turns into a stray paragraph.
* Add support for recoverable syntax errorsLibravatar Titus Wormer2022-09-071-64/+62
|
* Add support for GFM tablesLibravatar Titus Wormer2022-08-311-0/+1782