blackfriday v2.0.1 Release Notes

Release Date: 2018-09-23 // over 1 year ago
  • πŸš€ A minor release, mainly aimed at releasing a version with go.mod.

    • βž• Added go.mod
    • ✨ Enhanced support for info strings in fenced code blocks (issue #410)
    • ⚑️ README updates
    • βž• Added a reference to confluence wiki renderer
    • πŸ›  Fixed HTML entity regex
    • πŸ›  Fixed HTML5 by removing rel="footnote" which is invalid
    • βž• Added NoopenerLinks option that adds rel="noopener" attribute
    • βž• Added heading offset option to HTML renderer
    • πŸ›  Fixed consecutive lists of different kinds
    • πŸ›  Fixed block parsing for fenced code blocks in lists (issue #239)

    Huge thanks to the contributors!
    BjΓΈrn Erik Pedersen (@bep)
    Cameron Moore (@moorereason)
    Dmitri Shuralyov (@dmitshur)
    Emil Melnikov (@emilmelnikov)
    Iain Haslam (@understated)
    Kentaro Matsushita (@kentaro-m)
    Liming Jin (@jinliming2)
    Michael (@michael-k)
    Mitchell Cohen (@mitchchn)
    Nathan Glenn (@garfieldnate)
    Nick Galbreath (@client9)
    Rebecca Turner (@9999years)
    Vas Sudanagunta (@vassudanagunta)


Previous changes from v2.0.0

  • πŸ”– Version 2 of Blackfriday is a major overhaul of the API. Feature-wise nothing has changed, but the entire set of types, functions and constants has changed. This was done to make the API have more idiomatic Go look-and-feel, and fix a few bugs inherent in the legacy C-like interface. As a bonus, Blackfriday has become more flexible for extension.

    Highlights:

    • The most common entry point has been simplified. The vast majority of users can now call Run to get what they want:

      outputBytes := blackfriday.Run(inputBytes)

    • Writing your own renderer has become much easier.

    • 0️⃣ It's become very easy to write an extension to an existing renderer, customizing one aspect or another, and leaning back to the default behavior.

    • πŸ“œ You can now parse the Markdown document and obtain the syntax tree. You can manipulate the tree before rendering, or you can use it for data extraction from the Markdown documents.

    • πŸ“š To get all of the above working, documentation has been improved.