matrix-spec-proposals/scripts/templating/matrix_templates/templates/common-event-fields.tmpl

{% import 'tables.tmpl' as tables -%}

{{common_event.title}} Fields
{{(7 + common_event.title | length) * title_kind}}

{{common_event.desc}}

{% for table in common_event.tables %}

{{ tables.paramtable(table.rows, ["Key", "Type", "Description"], (table.title or "")) }}

{% endfor %}
Rewrite the table templates Allow columns to stretch if they end up with wide content. Apart from the hassle of having to manually update the calculations, having the columns wide enough to hold the widest thing they might ever have leads to tables with lots of whitespace in the results. 9 years ago			`{% import 'tables.tmpl' as tables -%}`

Rename 'type' field to 'title' : because that better reflects the underlying schema ("type" is one of object/string/etc). 7 years ago			`{{common_event.title}} Fields`
			`{{(7 + common_event.title \| length) * title_kind}}`
Add common event field descriptions and template. 9 years ago
Use standard logic to parse core event schemas Use process_data_type rather than reinventing our own wheel; doing so means that the 'Required' fields are correctly annotated as such. 7 years ago			`{{common_event.desc}}`
Add common event field descriptions and template. 9 years ago
Use standard logic to parse core event schemas Use process_data_type rather than reinventing our own wheel; doing so means that the 'Required' fields are correctly annotated as such. 7 years ago			`{% for table in common_event.tables %}`

sanitise caption handling 6 years ago			`{{ tables.paramtable(table.rows, ["Key", "Type", "Description"], (table.title or "")) }}`
Use standard logic to parse core event schemas Use process_data_type rather than reinventing our own wheel; doing so means that the 'Required' fields are correctly annotated as such. 7 years ago
			`{% endfor %}`