I was looking into using this sphinx extension to handle the MyST vs. rST comparison:<

Don't worry I've already taken care of it in <a href="https://github.com/ExecutableBoo

This PR will also handle the directive option indentation <a class="issue-link js-issu

Note - here is an example of code that causes this behavior: <a class="issue-link js-i

To clarify this issue: the docutils parser <a href="https://github.com/docutils-mirror

Replicate directive parsing behaviour of RST parser(?) about myst-parser HOT 8 CLOSED

executablebooks commented on May 24, 2024

Replicate directive parsing behaviour of RST parser(?)

from myst-parser.

Comments (8)

chrisjsewell commented on May 24, 2024 1

Don't worry I've already taken care of it in https://github.com/ExecutableBookProject/myst_parser/tree/restructure-testing, PR to come soon

from myst-parser.

chrisjsewell commented on May 24, 2024

Yeh no problem, I’ll look into it

from myst-parser.

choldgraf commented on May 24, 2024

I have been trying to figure out what's going on, and the only difference I can find between the MyST and the docutils statemachine seems to be in the parse_directive_arguments method:

    def parse_directive_arguments(directive, arg_text):

If I print a type on each iteration like so:

    def parse_directive_arguments(directive, arg_text):
        print(type(arg_text))

Then I get these outputs:

docutils function: <class 'docutils.statemachine.StringList'>
MyST function: <class 'str'>

No idea if that has something to do with this error, but I'm just trying to figure out where behavior is different between the two packages

from myst-parser.

chrisjsewell commented on May 24, 2024

It was because the CodeFence regex was including the line break character as part of the argument string.

from myst-parser.

chrisjsewell commented on May 24, 2024

This PR will also handle the directive option indentation #54

from myst-parser.

choldgraf commented on May 24, 2024

Note that this doesn't seem to be fixed. Now when I run the same code (after a rebase), I get a warning instead of a break, but it's the same warning (1 argument passed while 0 expected). Gonna re-open this so we don't lose track of it, in case there is an underlying issue that's causing this

from myst-parser.

choldgraf commented on May 24, 2024

Note - here is an example of code that causes this behavior: #60

from myst-parser.

chrisjsewell commented on May 24, 2024

To clarify this issue: 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); the <option block> can start at <arguments> or, if no required/optional arguments are specified and no options are specified; the <body> block can start at <arguments>. Examples:

.. content:: :depth: 2

.. note:: This is body text

from myst-parser.

Recommend Projects

Replicate directive parsing behaviour of RST parser(?) about myst-parser HOT 8 CLOSED

Comments (8)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent