Replies: 1 comment 1 reply
-
|
@jmduke you can handle this by creating a custom Pseudocode: import {nodes} from '@markdoc/markdoc'
// ...
nodes: {
fence: {
...nodes.fence,
attributes: {
...nodes.fence.attributes,
process: { ...nodes.fence.attributes.process, default: false },
}
}
}
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Thank you for your suggestion I'm trying to render markdoc code inside code fences, using markdoc (but not process and convert them into tags) I have been somewhat successful in preventing the tags being processed, but they now tags not displayed in the rendered fences. Is there a way to retain and render the tags? Sample codeimport Markdoc from '@markdoc/markdoc';
export function transformVanillaMarkdown(markdown: string) {
const vanillaConfig = {
nodes: {
fence: {
...Markdoc.nodes.fence,
attributes: {
...Markdoc.nodes.fence.attributes,
process: {
...Markdoc.nodes.fence.attributes.process,
default: false
}
}
}
}
const ast = Markdoc.parse(markdown);
const renderableTree = Markdoc.transform(ast, vanillaConfig);
return Markdoc.renderers.html(renderableTree);
}Input markdoc```markdown
# Welcome
Try writing some markdown here...
{% callout type="info" title="Markdown Tips" %}
You can use regular markdown syntax like **bold** and *italic*.
{% /callout %}
```Result<pre data-language="markdown"># Welcome
Try writing some markdown here...
You can use regular markdown syntax like **bold** and *italic*.
</pre>Expected Result<pre data-language="markdown"># Welcome
Try writing some markdown here...
{% callout type="info" title="Markdown Tips" %}
You can use regular markdown syntax like **bold** and *italic*.
{% /callout %}
</pre> |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We're porting our docs to Markdoc (backed by Keystatic) and got bitten pretty hard by the issue described in #72 and #306 because our docs have a lot of handlebar-ish code blocks, and it's somewhat hard to enforce the
process=falsetag in every single code block. @rpaul-stripe mentioned adding a global configuration for this and I'm opening this issue to formally suggest that.(I would also argue that the default should probably be
process=falserather thanprocess=true, but that's a different discussion!)Beta Was this translation helpful? Give feedback.
All reactions