mirror
/
datasette
kopia lustrzana https://github.com/simonw/datasette
1
0
Forkuj 0
Kod Zgłoszenia Packages Projekty Wydania Wiki Aktywność

Updated custom template docs, refs #521

better-templates
Simon Willison 2019-07-02 20:13:34 -07:00
rodzic 94d856c9a1
commit 1add905532
1 zmienionych plików z 21 dodań i 31 usunięć
Pokaż statystyki Ściągnij plik aktualizacji Ściągnij plik porównania Expand all files Collapse all files

52
docs/custom_templates.rst
Wyświetl plik

@ -144,12 +144,12 @@ The lookup rules Datasette uses are as follows::
row-mydatabase-mytable.html row-mydatabase-mytable.html
row.html row.html
Rows and columns include on table page: Table of rows and columns include on table page:
_table-table-mydatabase-mytable.html _table-table-mydatabase-mytable.html
_table-mydatabase-mytable.html _table-mydatabase-mytable.html
_table.html _table.html
Rows and columns include on row page: Table of rows and columns include on row page:
_table-row-mydatabase-mytable.html _table-row-mydatabase-mytable.html
_table-mydatabase-mytable.html _table-mydatabase-mytable.html
_table.html _table.html
@ -189,38 +189,28 @@ content you can do so by creating a ``row.html`` template like this::
Note the ``default:row.html`` template name, which ensures Jinja will inherit Note the ``default:row.html`` template name, which ensures Jinja will inherit
from the default template. from the default template.
The ``_table.html`` template is included on both the row and the table The ``_table.html`` template is included by both the row and the table pages,
page, and displays the content of the row. The default ``_table.html`` template and a list of rows. The default ``_table.html`` template renders them as an
`can be seen here <https://github.com/simonw/datasette/blob/master/datasette/templates/_table.html>`_. HTML template and `can be seen here <https://github.com/simonw/datasette/blob/master/datasette/templates/_table.html>`_.
You can provide a custom template that applies to all of your databases and You can provide a custom template that applies to all of your databases and
tables, or you can provide custom templates for specific tables using the tables, or you can provide custom templates for specific tables using the
template naming scheme described above. template naming scheme described above.
Say for example you want to output a certain column as unescaped HTML. You could If you want to present your data in a format other than an HTML table, you
provide a custom ``_table.html`` template like this:: can do so by looping through ``display_rows`` in your own ``_table.html``
template. You can use ``{{ row["column_name"] }}`` to output the raw value
of a specific column.
<table> If you want to output the rendered HTML version of a column, including any
<thead> links to foreign keys, you can use ``{{ row.display("column_name") }}``.
<tr>
{% for column in display_columns %} Here is an example of a custom ``_table.html`` template::
<th scope="col">{{ column }}</th>
{% endfor %} {% for row in display_rows %}
</tr> <div>
</thead> <h2>{{ row["title"] }}</h2>
<tbody> <p>{{ row["description"] }}<lp>
{% for row in display_rows %} <p>Category: {{ row.display("category_id") }}</p>
<tr> </div>
{% for cell in row %} {% endfor %}
<td>
{% if cell.column == 'description' %}
{{ cell.value|safe }}
{% else %}
{{ cell.value }}
{% endif %}
</td>
{% endfor %}
</tr>
{% endfor %}
</tbody>
</table>