Have the ability to use asciidoctor-doctest from the JavaScript Asciidoctor ecosystem

[obilodeau]

We are adding doctest support to asciidoctor-reveal.js and we are facing a problem where only our ruby-based slim templates will be testable using doctest and not our jade templates (used by AsciidocFX or anyone who prefers managing their slide decks with node/npm instead of ruby). Since reveal.js is a node/npm project it integrates well that way too.

It would be nice if we could use doctest from our asciidoctor-reveal.js plugin. This is an example of how it is used in the reveal.js context.

• http://asciidoctor.org/docs/install-and-use-asciidoctorjs/
• https://github.com/asciidoctor/asciidoctor.js

[obilodeau]

This is not gonna happen and the reasoning is sound: asciidoctor/asciidoctor-reveal.js#116 (comment)

[ggrossetie]

@jirutka @obilodeau I think this issue is still relevant no ?

Jakub was suggesting to be able to run a command line (ie. https://github.com/asciidoctor/asciidoctor-cli.js).

Currently AsciidocConverter is basically a wrapper around the Asciidoctor.convert Ruby API but we could configure this converter to run either the Ruby API or the JavaScript cli. Though this is not really extensible and I think a better solution should be to create multiple implementations:

• Asciidoctor Ruby API converter (default)
• Asciidoctor JavaScript cli converter (a specialized version of the command line converter) [optional]
• Command line converter

Ideas ? Thoughts ?

[obilodeau]

I thought that if we compiled the slim templates to Ruby and tested that with doctest in Ruby that it would suffice.

As I write this, I realize that this wouldn't catch regressions or issues introduced by Opal, Asciidoctor.js or our javascript build script.

[jirutka]

This is not gonna happen and the reasoning is sound…

Nope, it’s going to happen, i.e. DocTest will be able to run asciidoctor.js. This modularity was part of the refactoring effort, but it’s not done yet.

[ggrossetie]

@jirutka Do you already have a working branch for this refactoring or can I give it a try ?