For v3.0.1: indented directive options no longer recognised about myst-parser HOT 7 CLOSED

Cheers, yeh one of those things where an "implementation detail" becomes part of the spec lol;
I must have removed the lstrip when checking if a line is part of the option block, but didn't account for this possibility of having indented options.

from myst-parser.

Thanks for opening your first issue here! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out EBP's Code of Conduct. Also, please try to follow the issue template as it helps other community members to contribute more effectively.

If your issue is a feature request, others may react to it, to raise its prominence (see Feature Voting).

Welcome to the EBP community! 🎉

from myst-parser.

Heya, ah I think I know why this is, if you have the options without the indentation, it should work, e.g.

```{image} /_static/blog_images/neuroblueprint/NeuroBlueprint_project_tree_light.png
:align: center
:class: only-light
:width: 650px
```

let me know?

But yeh I can fix this regression (and add a test to catch it 😅) hopefully in the next day or two

from myst-parser.

Thanks for the quick response @chrisjsewell, that fixed it!! 😄 Cheers

from myst-parser.

I use backticks in the real version but use ::: here for formatting reasons

FYI you know you can just surround with more backticks, e.g.

``````outer
````inner
```more-inner
content
```
````
``````

from myst-parser.

But yeh I can fix this regression (and add a test to catch it 😅) hopefully in the next day or two

Thank you! We're seeing the same issue, with lots of warnings for all the indented options ...

from myst-parser.

I use backticks in the real version but use ::: here for formatting reasons

FYI you know you can just surround with more backticks, e.g.

``````outer
````inner
```more-inner
content

Awesome, thanks!!

from myst-parser.