Skip to content
Browse files

Clarify that new blocks are added to *container* blocks. (#598)

My first attempt at writing a parser added new blocks to the last
matched block, regardless if it was a container or leaf. I think it
would have helped me if it had explicitly said "container" here.
  • Loading branch information...
jayschwa authored and jgm committed Aug 5, 2019
1 parent 3991f05 commit 8b768f7701d22357815c36abf4b04d7616357e17
Showing with 1 addition and 1 deletion.
  1. +1 −1 spec.txt
@@ -9443,7 +9443,7 @@ blocks. But we cannot close unmatched blocks yet, because we may have a
blocks, we look for new block starts (e.g. `>` for a block quote).
If we encounter a new block start, we close any blocks unmatched
in step 1 before creating the new block as a child of the last
matched block.
matched container block.

3. Finally, we look at the remainder of the line (after block
markers like `>`, list markers, and indentation have been consumed).

0 comments on commit 8b768f7

Please sign in to comment.
You can’t perform that action at this time.