You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working on allowing markdown-formatted text in title, sub_title, text and name texts of sections.
My first approach was to use a setting to allow choosing between markdown and HTML rendering, defaulting to HTML for backward compat.
But, as markdown also allows plain HTML, I am wondering about just making it the only and default rendering option (simplifying documentation and use).
The major drawback I can think about would be for people who wrote HTML text with blank lines in it, that would get meaning and produce <p> in output. IMHO, that is an acceptable break (major version bump to indicate that ?).
Not a proof of anything, but I compiled my own galleries with my markdown patch without any difference in output.
So, two questions :
is that feature welcomed (PR ahead, already working locally) ?
what about making markdown rendering the default and only option ?
The text was updated successfully, but these errors were encountered:
I am working on allowing markdown-formatted text in
title
,sub_title
,text
andname
texts of sections.My first approach was to use a setting to allow choosing between markdown and HTML rendering, defaulting to HTML for backward compat.
But, as markdown also allows plain HTML, I am wondering about just making it the only and default rendering option (simplifying documentation and use).
The major drawback I can think about would be for people who wrote HTML text with blank lines in it, that would get meaning and produce
<p>
in output. IMHO, that is an acceptable break (major version bump to indicate that ?).Not a proof of anything, but I compiled my own galleries with my markdown patch without any difference in output.
So, two questions :
The text was updated successfully, but these errors were encountered: