All Versions
14
Latest Version
Avg Release Cycle
13 days
Latest Release
144 days ago

Changelog History
Page 1

  • v2.1.4

    March 16, 2020
    • #306 Make fail modifier work together with nest
  • v2.1.3

    March 13, 2020
  • v2.1.2

    March 12, 2020
    • #304 Catch fatal exceptions
    • 📚 #303 Improve cli --help documentation
    • 📄 #302 Improve mdoc:js installation docs
  • v2.1.1

    January 03, 2020
  • v2.1.0

    December 26, 2019

    What’s Changed

    Tips for moving from tut to mdoc

    Check out this post on migrating from tut to mdoc https://underscore.io/blog/posts/2019/12/12/tut-to-mdoc.html

    ⚡️ Internal updates

  • v2.0.3

    December 03, 2019

    What’s Changed

  • v2.0.2

    November 17, 2019

    What’s Changed

    🚀 Note, this release is only relevant for Metals, see scalameta/metals#1069

    • ➕ Add public API for evaluating worksheets. (#208) @olafurpg
  • v2.0.1

    November 13, 2019

    What’s Changed

    • ➕ Add test with returned literal type (#206) @valencik
    • ➕ Add support and tests for Literal type syntax (#205) @valencik
    • ➕ Add documentation for the new :reset-object modifier (#202) @olafurpg
  • v2.0.0

    November 02, 2019

    👍 Reveal.js support in HTML files

    It's now possible to run mdoc on both *.md and *.html files. This makes it possible to use mdoc when writing slides with Reveal.js in HTML files, a common use-case that was supported by tut but not in mdoc until now.

    👌 Support for any markdown flavor

    👍 Mdoc should now work with any flavor of markdown. Previously, mdoc only supported Commonmark and custom syntax like Jekyll {toc}, sbt-paradox, footnotes, and other markdown dialects would not be preserved. Now, mdoc only processes code fences and leaves the rest of the document unchanged.

    The only syntax that is processed by mdoc is code fences using this syntax

    ```scala mdoc
    ```
    

    and site variables using this syntax @VERSION@.

    💥 Breaking changes

    • ⬆️ Code fences are now by default wrapped in classes instead of objects, see #190. This means that code examples using extends AnyVal will result in a compiler warning. If you get the following errors when upgrading, add the mdoc:reset-object modifier to the enclosing code fence

      Value class may not be a member of another class The outer reference in this type test cannot be checked at run time.

    • 📜 It's no longer possible to reference site variables using the syntax ![VERSION]. Use @VERSION@ instead. This syntax was never documented on the website and it's no longer possible to support it with the new custom parser for Markdown code fences. The @VERSION@ syntax is more flexible since it works anywhere, including code fences, while the ![VERSION] syntax only worked in places where it was possible to write markdown links.

  • v1.4.0-RC3

    October 31, 2019