The renderer should correctly renders the given text or source content, not just viable when using the content parameter.
Actual behavior
I want to create a notation bubble (something like a dictionary) for the section which is able to be reused by defining a tag plugin, the notation is created in markdown format file. However, when I develop this tag plugin, I found something abnormal behavior from the hexo render.
TL;DR: The hexo render only renders correctly when directly using the content parameter. It can only render basic markdown, others like tag plugins, code block cannot be correctly rendered.
Retrieving the file content as the markdown content
Check List
hexo version
to check)Expected behavior
The renderer should correctly renders the given text or source content, not just viable when using the
content
parameter.Actual behavior
I want to create a notation bubble (something like a dictionary) for the section which is able to be reused by defining a tag plugin, the notation is created in markdown format file. However, when I develop this tag plugin, I found something abnormal behavior from the hexo render.
TL;DR: The hexo render only renders correctly when directly using the
content
parameter. It can only render basic markdown, others like tag plugins, code block cannot be correctly rendered.Retrieving the file content as the markdown content
bubble.js
here is the final HTML of the notation:
the result preview:
as you see, the fenced code block only defines the
<pre>
tag, instead of the hexo's modified one (figure
>table
)Retrieving content parameter as the markdown content
bubble2.js
the final HTML:
the result preview:
How to reproduce?
I found this bug when I trying to render markdown content that is not from
content
parameter.Is the problem still there under
Safe mode
?yes
Your Node.js & npm version
Your Hexo and Plugin version
Your
package.json
Your site's
_config.yml
(Optional)No response
Others
No response