Open juanmaguitar opened 3 weeks ago
thanks for the report @juanmaguitar! this isn't a problem with Markdown parsing, I don't believe, but rather a problem in Block printing to Markdown.
When this was quickly built I didn't cross all the t's and dot all the i's. You could fix this and enhance support by Markdown-escaping the output of the code block in the above-linked lines.
@juanmaguitar I tried to reproduce this just now and the code block is showing up as I expected it. I took the raw content from the ssh-in-github.md
file and then clicked on "Import from Markdown" in the block-formats sidebar. It displayed as a code block with pre-formatted whitespace.
Am I doing something different than you did?
@juanmaguitar is it possible you attempted to load the posts as markdown? my plugin isn't setup to load the markdown and convert it. that's found in the Edit Visually browser extension
I created a custom repo based on bgrgicak/playground-blog proof of concept. My repo is available at wordpress-juanmaguitar/playground-blog
in that repo I created a few markdown posts, under the
posts
folder, using code blocks and inline code textsThis is the link for the playground for that repo: https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/wordpress-juanmaguitar/playground-blog/main/blueprint.json
Code blocks were not properly parsed as it can be seen in the following screenshot:
cc: @bgrgicak @adamziel