A Markdown parser written in Go. Easy to extend, standards-compliant, well-structured.
goldmark is compliant with CommonMark 0.31.2.
There is also a Rust version of goldmark: rushdown
I needed a Markdown parser for Go that satisfies the following requirements:
golang-commonmark may be a good choice, but it seems to be a copy of markdown-it.
blackfriday.v2 is a fast and widely-used implementation, but is not CommonMark-compliant and cannot be extended from outside of the package, since its AST uses structs instead of interfaces.
Furthermore, its behavior differs from other implementations in some cases, especially regarding lists: Deep nested lists don't output correctly #329, List block cannot have a second line #244, etc.
This behavior sometimes causes problems. If you migrate your Markdown text from GitHub to blackfriday-based wikis, many lists will immediately be broken.
As mentioned above, CommonMark is complicated and hard to implement, so Markdown parsers based on CommonMark are few and far between.
@username mention syntax to Markdown?
You can easily do so in goldmark. You can add your AST nodes,
parsers for block-level elements, parsers for inline-level elements,
transformers for paragraphs, transformers for the whole AST structure, and
renderers.go test --fuzz.$ go get github.com/yuin/goldmark
Import packages:
import (
"bytes"
"github.com/yuin/goldmark"
)
Convert Markdown documents with the CommonMark-compliant mode:
var buf bytes.Buffer
if err := goldmark.Convert(source, &buf); err != nil {
panic(err)
}
var buf bytes.Buffer
if err := goldmark.Convert(source, &buf, parser.WithContext(ctx)); err != nil {
panic(err)
}
| Functional option | Type | Description |
|---|---|---|
parser.WithContext |
A parser.Context |
Context for the parsing phase. |
| Functional option | Type | Description |
|---|---|---|
parser.WithIDs |
A parser.IDs |
IDs allows you to change logics that are related to element id(ex: Auto heading id generation). |
import (
"bytes"
"github.com/yuin/goldmark"
"github.com/yuin/goldmark/extension"
"github.com/yuin/goldmark/parser"
"github.com/yuin/goldmark/renderer/html"
)
md := goldmark.New(
goldmark.WithExtensions(extension.GFM),
goldmark.WithParserOptions(
parser.WithAutoHeadingID(),
),
goldmark.WithRendererOptions(
html.WithHardWraps(),
html.WithXHTML(),
),
)
var buf bytes.Buffer
if err := md.Convert(source, &buf); err != nil {
panic(err)
}
| Functional option | Type | Description |
|---|---|---|
goldmark.WithParser |
parser.Parser |
This option must be passed before goldmark.WithParserOptions and goldmark.WithExtensions |
goldmark.WithRenderer |
renderer.Renderer |
This option must be passed before goldmark.WithRendererOptions and goldmark.WithExtensions |
goldmark.WithParserOptions |
...parser.Option |
|
goldmark.WithRendererOptions |
...renderer.Option |
|
goldmark.WithExtensions |
...goldmark.Extender |
| Functional option | Type | Description |
|---|---|---|
parser.WithBlockParsers |
A util.PrioritizedSlice whose elements are parser.BlockParser |
Parsers for parsing block level elements. |
parser.WithInlineParsers |
A util.PrioritizedSlice whose elements are parser.InlineParser |
Parsers for parsing inline level elements. |
parser.WithParagraphTransformers |
A util.PrioritizedSlice whose elements are parser.ParagraphTransformer |
Transformers for transforming paragraph nodes. |
parser.WithASTTransformers |
A util.PrioritizedSlice whose elements are parser.ASTTransformer |
Transformers for transforming an AST. |
parser.WithAutoHeadingID |
- |
Enables auto heading ids. |
parser.WithAttribute |
- |
Enables custom attributes. Currently only headings supports attributes. |
| Functional option | Type | Description |
|---|---|---|
html.WithWriter |
html.Writer |
html.Writer for writing contents to an io.Writer. |
html.WithHardWraps |
- |
Render newlines as ` |
.|
|html.WithXHTML|-| Render as XHTML. |
|html.WithUnsafe|-` | By default, goldmark does not render raw HTML or potentially dangerous links. With this option, goldmark renders such content as written. |
extension.Table
extension.Strikethrough
extension.Linkify
extension.TaskList
extension.GFMextension.DefinitionList
extension.Footnote
extension.Typographerextension.CJKThe parser.WithAttribute option allows you to define attributes on some elements.
Currently only headings support attributes.
Attributes are being discussed in the CommonMark forum. This syntax may possibly change in the future.
## heading ## {#id .className attrName=attrValue class="class1 class2"}
## heading {#id .className attrName=attrValue class="class1 class2"}
heading {#id .className attrName=attrValue}
============
The Table extension implements Table(extension), as defined in GitHub Flavored Markdown Spec.
Specs are defined for XHTML, so specs use some deprecated attributes for HTML5.
You can override alignment rendering method via options.
| Functional option | Type | Description |
|---|---|---|
extension.WithTableCellAlignMethod |
extension.TableCellAlignMethod |
Option indicates how are table cells aligned. |
The Typographer extension translates plain ASCII punctuation characters into typographic-punctuation HTML entities.
Default substitutions are:
| Punctuation | Default entity |
|---|---|
' |
‘, ’ |
" |
“, ” |
-- |
– |
--- |
— |
... |
… |
<< |
« |
>> |
» |
You can override the default substitutions via extensions.WithTypographicSubstitutions:
markdown := goldmark.New(
goldmark.WithExtensions(
extension.NewTypographer(
extension.WithTypographicSubstitutions(extension.TypographicSubstitutions{
extension.LeftSingleQuote: []byte("‚"),
extension.RightSingleQuote: nil, // nil disables a substitution
}),
),
),
)
The Linkify extension implements Autolinks(extension), as defined in GitHub Flavored Markdown Spec.
Since the spec does not define details about URLs, there are numerous ambiguous cases.
You can override autolinking patterns via options.
| Functional option | Type | Description |
|---|---|---|
extension.WithLinkifyAllowedProtocols |
[][]byte \| []string |
List of allowed protocols such as []string{ "http:" } |
extension.WithLinkifyURLRegexp |
*regexp.Regexp |
Regexp that defines URLs, including protocols |
extension.WithLinkifyWWWRegexp |
*regexp.Regexp |
Regexp that defines URL starting with www.. This pattern corresponds to the extended www autolink |
extension.WithLinkifyEmailRegexp |
*regexp.Regexp |
Regexp that defines email addresses` |
Example, using xurls:
import "mvdan.cc/xurls/v2"
markdown := goldmark.New(
goldmark.WithRendererOptions(
html.WithXHTML(),
html.WithUnsafe(),
),
goldmark.WithExtensions(
extension.NewLinkify(
extension.WithLinkifyAllowedProtocols([]string{
"http:",
"https:",
}),
extension.WithLinkifyURLRegexp(
xurls.Strict(),
),
),
),
)
The Footnote extension implements PHP Markdown Extra: Footnotes.
This extension has some options:
| Functional option | Type | Description |
|---|---|---|
extension.WithFootnoteIDPrefix |
[]byte \| string |
a prefix for the id attributes. |
extension.WithFootnoteIDPrefixFunction |
func(gast.Node) []byte |
a function that determines the id attribute for given Node. |
extension.WithFootnoteLinkTitle |
[]byte \| string |
an optional title attribute for footnote links. |
extension.WithFootnoteBacklinkTitle |
[]byte \| string |
an optional title attribute for footnote backlinks. |
extension.WithFootnoteLinkClass |
[]byte \| string |
a class for footnote links. This defaults to footnote-ref. |
extension.WithFootnoteBacklinkClass |
[]byte \| string |
a class for footnote backlinks. This defaults to footnote-backref. |
extension.WithFootnoteBacklinkHTML |
[]byte \| string |
a class for footnote backlinks. This defaults to ↩︎. |
Some options can have special substitutions. Occurrences of “^^” in the string will be replaced by the corresponding footnote number in the HTML output. Occurrences of “%%” will be replaced by a number for the reference (footnotes can have multiple references).
extension.WithFootnoteIDPrefix and extension.WithFootnoteIDPrefixFunction are useful if you have multiple Markdown documents displayed inside one HTML document to avoid footnote ids to clash each other.
extension.WithFootnoteIDPrefix sets fixed id prefix, so you may write codes like the following:
```go for _, path := range files { source := readAll(path) prefix := getPrefix(path)
markdo
$ claude mcp add goldmark \
-- python -m otcore.mcp_server <graph>