markdown-rs - CommonMark compliant markdown parser in Rust with ASTs and extensions

	Commit message (Collapse)	Author	Files	Lines
2022-11-10	Remove unneeded `extern crate`s	Hocdoc	1	-1/+0
	Closes GH-28. Co-authored-by: Bernhard Berger <bernhardberger3456@gmail.com>
2022-10-28	Fix GFM tables to require a non-pipe in header row	Titus Wormer	1	-0/+18
	Related-to: GH-20.
2022-10-14	Refactor to use default trait in tests	Titus Wormer	1	-107/+77

2022-10-13	Remove some unused code in gfm tables	Titus Wormer	1	-0/+19

2022-10-13	Rename crate to `markdown`	Titus Wormer	1	-67/+67

2022-10-11	Refactor to use a bunch of `into`	Titus Wormer	1	-11/+11

2022-10-06	Refactor to split parse from compile options	Titus Wormer	1	-30/+72

2022-09-28	Add support for turning mdast to hast	Titus Wormer	1	-2/+4

2022-09-26	Add support for compiling to mdast	Titus Wormer	1	-1/+131
	See: <https://github.com/syntax-tree/mdast>.
2022-09-19	Add support for parsing MDX ESM, expressions	Titus Wormer	1	-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).
2022-09-14	Fix to prefer flow over definitions, setext headings	Titus Wormer	1	-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.
2022-09-07	Add support for recoverable syntax errors	Titus Wormer	1	-64/+62

2022-08-31	Add support for GFM tables	Titus Wormer	1	-0/+1782