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
Since we have directives and roles that could make HTML at a block or in-line level explicit (rather than detected with regexes and such), what do folks think about explicitly not allowing raw HTML in the myst content, and instead asking people to use a directive or role if they want to embed HTML in their page?
The text was updated successfully, but these errors were encountered:
To be compliant with CommonMark, it has to at least detect it anyway, even if it is later ignored. So I don’t see much benefit in disallowing it, although obviously it should be discouraged.
Yeah - I had the same thought re: breaking spec w/ CommonMark. I think it's a good idea to explicitly discourage it in the docs. I'll add that in a little PR
Since we have directives and roles that could make HTML at a block or in-line level explicit (rather than detected with regexes and such), what do folks think about explicitly not allowing raw HTML in the myst content, and instead asking people to use a directive or role if they want to embed HTML in their page?
The text was updated successfully, but these errors were encountered: