-
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Q&A against documentation" on the datasette.io homepage #13
Comments
Here's the YAML: https://github.com/simonw/datasette.io/blob/b821fb19eda08b4942183db507bb6f986f8134bf/news.yaml#L3 The markdown is stored in the DB: https://datasette.io/content/news?_sort=rowid&date__exact=2023-01-13 And rendered here: |
So it looks like |
This tool compares different markdown implementations: It suggests that |
I think this is likely a bug in the interaction between the markdown rendering and Bleach in this plugin: datasette-render-markdown/datasette_render_markdown/__init__.py Lines 75 to 80 in c04b0b6
I can recreate it locally like this: >>> from datasette_render_markdown import render_markdown
>>> render_markdown('[this & that](https://www.example.com/)')
Markup('<div style="white-space: normal"><p><a href="https://www.example.com/" rel="nofollow">this &amp; that</a></p></div>') Note |
Confirmed: I removed the calls to bleach and got this:
|
After more exploration, it turns out it's the call to |
https://bleach.readthedocs.io/en/latest/linkify.html says:
|
Fix for double-escaped ampersand bug, refs simonw/datasette-render-markdown#13
Deployed that fix to https://datasette.io/ |
The text was updated successfully, but these errors were encountered: