Home

Awesome

Flexmark Icon Logo flexmark-java

flexmark-java is a Java implementation of CommonMark (spec 0.28) parser using the blocks first, inlines after Markdown parsing architecture.

Its strengths are speed, flexibility, Markdown source element based AST with details of the source position down to individual characters of lexemes that make up the element and extensibility.

The API allows granular control of the parsing process and is optimized for parsing with a large number of installed extensions. The parser and extensions come with plenty of options for parser behavior and HTML rendering variations. The end goal is to have the parser and renderer be able to mimic other parsers with great degree of accuracy. This is now partially complete with the implementation of Markdown Processor Emulation

Motivation for this project was the need to replace pegdown parser in my Markdown Navigator plugin for JetBrains IDEs. pegdown has a great feature set but its speed in general is less than ideal and for pathological input either hangs or practically hangs during parsing.

:warning: Version 0.60.0 has breaking changes due to re-organization, renaming, clean up and optimization of implementation classes. Changes are detailed in Version-0.60.0-Changes.

latest Maven Central status<!-- @IGNORE PREVIOUS: link --> Javadocs

Requirements

Quick Start

For Maven, add flexmark-all as a dependency which includes core and all modules to the following sample:

<dependency>
    <groupId>com.vladsch.flexmark</groupId>
    <artifactId>flexmark-all</artifactId>
    <version>0.64.8</version>
</dependency>

Source: BasicSample.java

package com.vladsch.flexmark.samples;

import com.vladsch.flexmark.util.ast.Node;
import com.vladsch.flexmark.html.HtmlRenderer;
import com.vladsch.flexmark.parser.Parser;
import com.vladsch.flexmark.util.data.MutableDataSet;

public class BasicSample {
    public static void main(String[] args) {
        MutableDataSet options = new MutableDataSet();

        // uncomment to set optional extensions
        //options.set(Parser.EXTENSIONS, Arrays.asList(TablesExtension.create(), StrikethroughExtension.create()));

        // uncomment to convert soft-breaks to hard breaks
        //options.set(HtmlRenderer.SOFT_BREAK, "<br />\n");

        Parser parser = Parser.builder(options).build();
        HtmlRenderer renderer = HtmlRenderer.builder(options).build();

        // You can re-use parser and renderer instances
        Node document = parser.parse("This is *Sparta*");
        String html = renderer.render(document);  // "<p>This is <em>Sparta</em></p>\n"
        System.out.println(html);
    }
}

Building via Gradle

implementation 'com.vladsch.flexmark:flexmark-all:0.64.8'

Building with Android Studio

Additional settings due to duplicate files:

packagingOptions {
    exclude 'META-INF/LICENSE-LGPL-2.1.txt'
    exclude 'META-INF/LICENSE-LGPL-3.txt'
    exclude 'META-INF/LICENSE-W3C-TEST'
    exclude 'META-INF/DEPENDENCIES'
}

More information can be found in the documentation:
Wiki Home     Usage Examples     Extension Details     Writing Extensions

Pegdown Migration Helper

PegdownOptionsAdapter class converts pegdown Extensions.* flags to flexmark options and extensions list. Pegdown Extensions.java is included for convenience and new options not found in pegdown 1.6.0. These are located in flexmark-profile-pegdown module but you can grab the source from this repo: PegdownOptionsAdapter.java, Extensions.java and make your own version, modified to your project's needs.

You can pass your extension flags to static PegdownOptionsAdapter.flexmarkOptions(int) or you can instantiate PegdownOptionsAdapter and use convenience methods to set, add and remove extension flags. PegdownOptionsAdapter.getFlexmarkOptions() will return a fresh copy of DataHolder every time with the options reflecting pegdown extension flags.

import com.vladsch.flexmark.html.HtmlRenderer;
import com.vladsch.flexmark.parser.Parser;
import com.vladsch.flexmark.profile.pegdown.Extensions;
import com.vladsch.flexmark.profile.pegdown.PegdownOptionsAdapter;
import com.vladsch.flexmark.util.data.DataHolder;

public class PegdownOptions {
     final private static DataHolder OPTIONS = PegdownOptionsAdapter.flexmarkOptions(
            Extensions.ALL
    );

    static final Parser PARSER = Parser.builder(OPTIONS).build();
    static final HtmlRenderer RENDERER = HtmlRenderer.builder(OPTIONS).build();

    // use the PARSER to parse and RENDERER to render with pegdown compatibility
}

Default flexmark-java pegdown emulation uses less strict HTML block parsing which interrupts an HTML block on a blank line. Pegdown only interrupts an HTML block on a blank line if all tags in the HTML block are closed.

To get closer to original pegdown HTML block parsing behavior use the method which takes a boolean strictHtml argument:

import com.vladsch.flexmark.html.HtmlRenderer;
import com.vladsch.flexmark.parser.Parser;
import com.vladsch.flexmark.profile.pegdown.Extensions;
import com.vladsch.flexmark.profile.pegdown.PegdownOptionsAdapter;
import com.vladsch.flexmark.util.data.DataHolder;

public class PegdownOptions {
     final private static DataHolder OPTIONS = PegdownOptionsAdapter.flexmarkOptions(true,
            Extensions.ALL
    );

    static final Parser PARSER = Parser.builder(OPTIONS).build();
    static final HtmlRenderer RENDERER = HtmlRenderer.builder(OPTIONS).build();

    // use the PARSER to parse and RENDERER to render with pegdown compatibility
}

A sample with a custom link resolver is also available, which includes link resolver for changing URLs or attributes of links and a custom node renderer if you need to override the generated link HTML.

:information_source: flexmark-java has many more extensions and configuration options than pegdown in addition to extensions available in pegdown 1.6.0. Available Extensions via PegdownOptionsAdapter

Latest Additions and Changes

Releases, Bug Fixes, Enhancements and Support

I use flexmark-java as the parser for Markdown Navigator plugin for JetBrains IDEs. I tend to use the latest, unreleased version to fix bugs or get improvements. So if you find a bug that is a show stopper for your project or see a bug in github issues page marked fixed for next release that is affecting your project then please let me know and I may be able to promptly make a new release to address your issue. Otherwise, I will let bug fixes and enhancements accumulate thinking no one is affected by what is already fixed.

Extension points in the API are many and numerous

There are many extension options in the API with their intended use. A good soft-start is the flexmark-java-samples module which has simple samples for asked for extensions. The next best place is the source of an existing extension that has similar syntax to what you want to add.

If your extension lines up with the right API, the task is usually very short and sweet. If your extension uses the API in an unintended fashion or does not follow expected housekeeping protocols, you may find it an uphill battle with a rat's nest of if/else condition handling and fixing one bug only leading to creating another one.

Generally, if it takes more than a few dozen lines to add a simple extension, then either you are going about it wrong or the API is missing an extension point. If you look at all the implemented extensions you will see that most are a few lines of code other than boiler plate dictated by the API. That is the goal for this library: provide an extensible core that makes writing extensions a breeze.

The larger extensions are flexmark-ext-tables and flexmark-ext-spec-example, the meat of both is around 200 lines of code. You can use them as a guide post for size estimating your extension.

My own experience adding extensions shows that sometimes a new type of extension is best addressed with an API enhancement to make its implementation seamless, or by fixing a bug that was not visible before the extension stressed the API in just the right way. Your intended extension may just be the one requiring such an approach.

Don't hesitate to open an issue if you can't find the answer

The takeaway is: if you want to implement an extension or a feature please don't hesitate to open an issue and I will give you pointers on the best way to go about it. It may save you a lot of time by letting me improve the API to address your extension's needs before you put a lot of fruitless effort into it.

I do ask that you realize that I am chief cook and bottle washer on this project, without an iota of Vulcan Mind Melding skills. I do ask that you describe what you want to implement because I can't read your mind. Please do some reconnaissance background work around the source code and documentation because I cannot transfer what I know to you, without your willing effort.

Consulting is available

If you have a commercial application and don't want to write the extension(s) yourself or want to reduce the time and effort of implementing extensions and integrating flexmark-java, feel free to contact me. I am available on a consulting/contracting basis.

Markdown Processor Emulation

Despite its name, commonmark is neither a superset nor a subset of other markdown flavors. Rather, it proposes a standard, unambiguous syntax specification for the original, "core" Markdown, thus effectively introducing yet another flavor. While flexmark is by default commonmark compliant, its parser can be tweaked in various ways. The sets of tweaks required to emulate the most commonly used markdown parsers around are available in flexmark as ParserEmulationProfiles.

As the name ParserEmulationProfile implies, it's only the parser that is adjusted to the specific markdown flavor. Applying the profile does not add features beyond those available in commonmark. If you want to use flexmark to fully emulate another markdown processor's behavior, you have to adjust the parser and configure the flexmark extensions that provide the additional features available in the parser that you want to emulate.

A rewrite of the list parser to better control emulation of other markdown processors as per Markdown Processors Emulation is complete. Addition of processor presets to emulate specific markdown processing behaviour of these parsers is on a short to do list.

Some emulation families do a better better job of emulating their target than others. Most of the effort was directed at emulating how these processors parse standard Markdown and list related parsing specifically. For processors that extend original Markdown, you will need to add those extensions that are already implemented in flexmark-java to the Parser/Renderer builder options.

Extensions will be modified to include their own presets for specific processor emulation, if that processor has an equivalent extension implemented.

If you find a discrepancy please open an issue so it can be addressed.

Major processor families are implemented and some family members also:

:information_source: profiles to encapsulate configuration details for variants within the family were added in 0.11.0:

History and Motivation

flexmark-java is a fork of commonmark-java project, modified to generate an AST which reflects all the elements in the original source, full source position tracking for all elements in the AST and easier JetBrains Open API PsiTree generation.

The API was changed to allow more granular control of the parsing process and optimized for parsing with a large number of installed extensions. The parser and extensions come with many tweaking options for parser behavior and HTML rendering variations. The end goal is to have the parser and renderer be able to mimic other parsers with great degree of accuracy.

Motivation for this was the need to replace pegdown parser in Markdown Navigator plugin. pegdown has a great feature set but its speed in general is less than ideal and for pathological input either hangs or practically hangs during parsing.

commonmark-java has an excellent parsing architecture that is easy to understand and extend. The goal was to ensure that adding source position tracking in the AST would not change the ease of parsing and generating the AST more than absolutely necessary.

Reasons for choosing commonmark-java as the parser are: speed, ease of understanding, ease of extending and speed. Now that I have reworked the core and added a few extensions I am extremely satisfied with my choice.

Another goal was to improve the ability of extensions to modify parser behavior so that any dialect of markdown could be implemented through the extension mechanism. An extensible options API was added to allow setting of all options in one place. Parser, renderer and extensions use these options for configuration, including disabling some core block parsers.

This is a work in progress with many API changes. No attempt is made to keep backward API compatibility to the original project and until the feature set is mostly complete, not even to earlier versions of this project.

Feature Comparison

Featureflexmark-javacommonmark-javapegdown
Relative parse time (less is better):heavy_check_mark: 1x (1):heavy_check_mark: 0.6x to 0.7x (2):x: 25x average, 20,000x to ∞ for pathological input (3)
All source elements in the AST:heavy_check_mark::x::heavy_check_mark:
AST elements with source position:heavy_check_mark::heavy_check_mark::heavy_check_mark: with some errors and idiosyncrasies
AST can be easily manipulated:heavy_check_mark: AST post processing is an extension mechanism:heavy_check_mark: AST post processing is an extension mechanism:x: not an option. No node's parent information, children as List<>.
AST elements have detailed source position for all parts:heavy_check_mark::x::x: only node start/end
Can disable core parsing features:heavy_check_mark::x::x:
Core parser implemented via the extension API:heavy_check_mark::x: instanceOf tests for specific block parser and node classes:x: core exposes few extension points
Easy to understand and modify parser implementation:heavy_check_mark::heavy_check_mark::x: one PEG parser with complex interactions (3)
Parsing of block elements is independent from each other:heavy_check_mark::heavy_check_mark::x: everything in one PEG grammar
Uniform configuration across: parser, renderer and all extensions:heavy_check_mark::x: none beyond extension list:x: int bit flags for core, none for extensions
Parsing performance optimized for use with extensions:heavy_check_mark::x: parsing performance for core, extensions do what they can:x: performance is not a feature
Feature rich with many configuration options and extensions out of the box:heavy_check_mark::x: limited extensions, no options:heavy_check_mark:
Dependency definitions for processors to guarantee the right order of processing:heavy_check_mark::x: order specified by extension list ordering, error prone:x: not applicable, core defines where extension processing is added
<!-- | | :x: | :x: | :x: | | | :x: | :x: | :x: | | | :x: | :x: | :x: | | | :x: | :x: | :x: | | | :x: | :x: | :x: | |--|:----|:----|:----| | | :x: | :x: | :x: | -->
(1)

flexmark-java pathological input of 100,000 [ parses in 68ms, 100,000 ] in 57ms, 100,000 nested [ ] parse in 55ms

(2)

commonmark-java pathological input of 100,000 [ parses in 30ms, 100,000 ] in 30ms, 100,000 nested [ ] parse in 43ms

(3)

pegdown pathological input of 17 [ parses in 650ms, 18 [ in 1300ms

Progress

I am very pleased with the decision to switch to commonmark-java based parser for my own projects. Even though I had to do major surgery on its innards to get full source position tracking and AST that matches source elements, it is a pleasure to work with and is now a pleasure to extend. If you don't need source level element AST or the rest of what flexmark-java added and CommonMark is your target markdown parser then I encourage you to use commonmark-java as it is an excellent choice for your needs and its performance does not suffer for the overhead of features that you will not use.

Benchmarks

Latest, Jan 28, 2017 flexmark-java 0.13.1, intellij-markdown from CE EAP 2017, commonmark-java 0.8.0:

Filecommonmark-javaflexmark-javaintellij-markdownpegdown
README-SLOW0.420ms0.812ms2.027ms15.483ms
VERSION0.743ms1.425ms4.057ms42.936ms
commonMarkSpec31.025ms44.465ms600.654ms575.131ms
markdown_example8.490ms10.502ms223.593ms983.640ms
spec4.719ms6.249ms35.883ms307.176ms
table0.229ms0.623ms0.800ms3.642ms
table-format1.385ms2.881ms4.150ms23.592ms
wrap3.804ms4.589ms16.609ms86.383ms

Ratios of above:

Filecommonmark-javaflexmark-javaintellij-markdownpegdown
README-SLOW1.001.934.8336.88
VERSION1.001.925.4657.78
commonMarkSpec1.001.4319.3618.54
markdown_example1.001.2426.34115.86
spec1.001.327.6065.09
table1.002.723.4915.90
table-format1.002.083.0017.03
wrap1.001.214.3722.71
overall1.001.4117.4740.11
Filecommonmark-javaflexmark-javaintellij-markdownpegdown
README-SLOW0.521.002.5019.07
VERSION0.521.002.8530.12
commonMarkSpec0.701.0013.5112.93
markdown_example0.811.0021.2993.66
spec0.761.005.7449.15
table0.371.001.285.85
table-format0.481.001.448.19
wrap0.831.003.6218.83
overall0.711.0012.4128.48

Because these two files represent the pathological input for pegdown, I no longer run them as part of the benchmark to prevent skewing of the results. The results are here for posterity.

Filecommonmark-javaflexmark-javaintellij-markdownpegdown
hang-pegdown0.082ms0.326ms0.342ms659.138ms
hang-pegdown20.048ms0.235ms0.198ms1312.944ms

Ratios of above:

Filecommonmark-javaflexmark-javaintellij-markdownpegdown
hang-pegdown1.003.984.178048.38
hang-pegdown21.004.864.1027207.32
overall1.004.304.1515151.91
Filecommonmark-javaflexmark-javaintellij-markdownpegdown
hang-pegdown0.251.001.052024.27
hang-pegdown20.211.000.845594.73
overall0.231.000.963519.73

Contributing

Pull requests, issues and comments welcome :smile:. For pull requests:

License

Copyright (c) 2015-2016 Atlassian and others.

Copyright (c) 2016-2023, Vladimir Schneider,

BSD (2-clause) licensed, see LICENSE.txt file.