text: support fenced code blocks in Markdown#4585
Conversation
My particular use case is dumping a json config file, but the fenced code syntax is pretty common in markdown and I suspect it will have lots of uses. https://www.markdownguide.org/extended-syntax/#fenced-code-blocks
|
Thanks for the PR! This seems pretty reasonable to me. Let me take a
You can prepend four spaces to each line, thus: ```
I am
a code block.
```
I am normal text.
I am also
a code block.But fenced code blocks are often more convenient, to be sure. |
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
|
@googlebot I consent. |
|
(Test sync passes: http://cl/352909055.) |
My particular use case is dumping a json config file, but the fenced code syntax is pretty common in markdown and I suspect it will have lots of uses.
https://www.markdownguide.org/extended-syntax/#fenced-code-blocks
Just adds the
fenced_codeextension.Log a text event with a fenced code block, verify it renders correctly.
I don't know another good way to include a block of preformatted text.