datasette-render-html
This Datasette plugin lets you configure Datasette to render specific columns as HTML in the table and row interfaces.
This means you can store HTML in those columns and have it rendered as such on those pages.
If you have a database called docs.db containing a glossary table and you want the definition column in that table to be rendered as HTML, you would use a metadata.json file that looks like this:
{
"databases": {
"docs": {
"tables": {
"glossary": {
"plugins": {
"datasette-render-html": {
"columns": ["definition"]
}
}
}
}
}
}
}
Metadata
Release files for datasette-render-html 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| datasette_render_html-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for datasette_render_html-0.1.1-py3-none-any.whl |
Release files / datasette_render_html-0.1.1-py3-none-any.whl
| Download URL | datasette_render_html-0.1.1-py3-none-any.whl |
|---|---|
| Size | 2.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0f0cd16c08a42472de9d9e2f358fb53372f68d39ad4d4f60e37269799649f984
|
|
BLAKE2b-256 checksum How to use checksums |
4f62a63f7a91d5aecf9a7b9048b86df6c906b1a9df2711703074e8d8c1995bb2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/40.6.2 requests-toolbelt/0.9.1 tqdm/4.43.0 CPython/3.6.10
|
Security for datasette-render-html 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.