-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
Support markdown and/or HTML in dashboard descriptions #115
Comments
This is a great idea - especially since we already bundle the Markdown library for other purposes. I think the simplest solution here would be to say that the dashboard description field supports markdown - I don't expect there to be wide enough deployments of the tool that treating existing descriptions as markdown is likely to break anything significant, though we'll still call it out in the release notes. |
Nice! Would you like me to start a PR for this or any of the other issues? I'm interested in giving back to this codebase but I also understand if you'd rather do things yourself. |
Would welcome a PR for this! |
This is now released as version 0.16. https://github.com/simonw/django-sql-dashboard/releases/tag/0.16 |
This upgrades us to django-sql-dashboard 1.0.1, which includes a few contributions of my own: * [The dashboard admin list view links to change views that the user may not have permission to use](simonw/django-sql-dashboard#130) * [Support markdown and/or HTML in dashboard descriptions](simonw/django-sql-dashboard#115)
In particular, I'm linking out to external sites in my dashboard descriptions, so it would be great to have those hyperlinked (currently the viewer has to manually copy/paste the URL, which is shown as plain text). Since the package already has both
markdown
andbleach
as dependencies, it doesn't seem like this should be technically complex, although perhaps making it backwards-compatible might be non-trivial...Anyways, happy to discuss this further and start a PR if it's deemed a good idea.
The text was updated successfully, but these errors were encountered: