You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you put a block break inside an admonition (or other content container), it is not respected and converted into a block. Instead, it remains a blockBreak in the final AST. This is easy to recreate, simply something like:
```{note}
This sentence is not in a block.
+++
This sentence should be in a block.
```
We will need to refactor that to traverse the entire tree for blockBreaks rather than just looking at top-level children. Hopefully we can still keep this in myst-parse, as much of the later processing already assumes block nodes exist.
The text was updated successfully, but these errors were encountered:
If you put a block break inside an admonition (or other content container), it is not respected and converted into a
block
. Instead, it remains ablockBreak
in the final AST. This is easy to recreate, simply something like:Currently this
blockBreak
->block
transformation occurs very early during processing, inmyst-parse
: https://github.com/jupyter-book/mystmd/blob/main/packages/myst-parser/src/tokensToMyst.ts#L574-L594We will need to refactor that to traverse the entire tree for
blockBreaks
rather than just looking at top-level children. Hopefully we can still keep this inmyst-parse
, as much of the later processing already assumesblock
nodes exist.The text was updated successfully, but these errors were encountered: