Improve directive block parsing #79

chrisjsewell · 2020-02-24T09:23:53Z

fixes #55

Firstly, the directive block text -> arguments, options, body parsing has been separated into to a standalone module.

Secondly, the docutils parser here
does not rigidly specify the structure of the directive block:

.. <name>:: <arguments>
    <option block>

   <body>

Instead, if no required/optional arguments are specified (by the directive class), and no <option block> is used, the <body> block can start at <arguments>. Example:

.. note:: This is body text

This PR allows MyST to implement that logic.

```{note} This is body text
```

Note the rST parser also allows for the options to start on the argument line.
But this PR does not implement that, because it doesn't integrate particularly well with the concept of YAML blocks.
Example:

.. content:: :depth: 2

chrisjsewell added 3 commits February 24, 2020 19:06

Move directive parsing code to seperate module

66ce80e

Allow content to start on argument block (if no arguments allowed)

ff4454d

Update syntax.md

9618158

chrisjsewell merged commit a171075 into develop Feb 24, 2020

chrisjsewell mentioned this pull request Feb 24, 2020

[DNM] showing off weird syntax w/ tabs directive #60

Closed

chrisjsewell deleted the directive-parsing branch February 24, 2020 09:56

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Improve directive block parsing #79

Improve directive block parsing #79

chrisjsewell commented Feb 24, 2020 •

edited

Improve directive block parsing #79

Improve directive block parsing #79

Conversation

chrisjsewell commented Feb 24, 2020 • edited

chrisjsewell commented Feb 24, 2020 •

edited