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
Blades seems to automatically wrap the summary of a page in these tags, since I get them in my normal template as well. Why? How about making it so {{summary}} doesn't automatically get wrapped and relying on the user to make sure they are marked up correctly, and the feed will be valid as well?
The text was updated successfully, but these errors were encountered:
The summary field had markdown support enabled and by default, pulldown_cmark puts text inside <p> tags.
Before Ramhorns 1.0 is released, the only way to avoid this is either to specifically implement the Content trait for a custom type, or to remove the markdown support for this field altogether.
I've opted for the latter in the commit a220b84.
Edit: commit number.
I'm a complete Rust noob but dove into the code of ramhorns and pulldown_cmark and got to the conclusion that this would require a custom cmark parser in ramhorns that filters Tags that indicate block-level Elements (and errors when one is found). But now I see ramhorns wants to implement Markdown support entirely differently?
Thanks for the fast reaction and fix, anyway! (By the way, you linked the wrong commit: a220b84)
According to https://stackoverflow.com/questions/7203450/what-paragraphs-and-line-breaks-are-valid-rss-formatting#comment8810661_7203450 (and other sources on the internet),
<p>
tags inside<description>
violate the RSS spec.Blades seems to automatically wrap the summary of a page in these tags, since I get them in my normal template as well. Why? How about making it so
{{summary}}
doesn't automatically get wrapped and relying on the user to make sure they are marked up correctly, and the feed will be valid as well?The text was updated successfully, but these errors were encountered: