Access to the parser in Asciidoctorjs

Hi everyone,

I am trying to lint text in asciidoctor documents.
Being able to access the tokens generated by the parser would help me a great deal with it.
From there it would  possible to skip code blocks or to be sure to run the linter on text nodes only.

If someone could point me the way to do it in Ruby, maybe I can figure out a way to to it with asciidoctorjs (I'm working in node).

Thanks in advance!

PS: marked gives access to its parser, which is pretty awesome!

---

If you reply to this email, your message will be added to the discussion below:

http://discuss.asciidoctor.org/Access-to-the-parser-in-Asciidoctorjs-tp4383.html

To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML

Asciidoctor does not provide low-level access to tokens. But there are various ways to interact with the AST that it does produce to accomplish your goal.

The main entry point is the document and from there the list of blocks. See:

* http://www.rubydoc.info/gems/asciidoctor/Asciidoctor/Document

* http://www.rubydoc.info/gems/asciidoctor/Asciidoctor/Block

* http://www.rubydoc.info/gems/asciidoctor/Asciidoctor/AbstractBlock#find_by-instance_method

That's a deep as it goes at the moment since the inline parsing is handled in a streaming fashion. That's why we have issue https://github.com/asciidoctor/asciidoctor/issues/61.

In order to do all this in Asciidoctor.js, I recommend writing it in Ruby and compiling it to JavaScript using Opal. It's possible to access the AST from JavaScript, but the API is somewhat awkward. Still, it's workable once you get used to it.

I recommend studying the chrome extension {1} and docgist {2} to see Asciidoctor.js in action.

-Dan

:1: https://github.com/asciidoctor/asciidoctor-chrome-extension

:2: https://github.com/asciidoctor/docgist

On Tue, Feb 23, 2016 at 8:26 AM, geowarin [via Asciidoctor :: Discussion] <[hidden email]> wrote:

Hi everyone,

I am trying to lint text in asciidoctor documents.
Being able to access the tokens generated by the parser would help me a great deal with it.
From there it would  possible to skip code blocks or to be sure to run the linter on text nodes only.

If someone could point me the way to do it in Ruby, maybe I can figure out a way to to it with asciidoctorjs (I'm working in node).

Thanks in advance!

PS: marked gives access to its parser, which is pretty awesome!

---

If you reply to this email, your message will be added to the discussion below:

http://discuss.asciidoctor.org/Access-to-the-parser-in-Asciidoctorjs-tp4383.html

To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML

... [show rest of quote]

--

Dan Allen | @mojavelinux | http://google.com/profiles/dan.j.allen