SemanticSchemas: SemanticSchemas: Auto-generated form

2026-04-27T14:24:33Z

SemanticSchemas: Auto-generated form

New page

<noinclude>


</noinclude><includeonly>
{{#if:{{{subobject|}}}|<h3>Subobject field</h3>|<h2>Subobject field</h2>}}

{{#if:{{{subobject|}}}
|{{#if:{{{required|}}}
|<nowiki>{{{for template|Subobject field/subobject|multiple|minimum instances=1}}}</nowiki>
|<nowiki>{{{for template|Subobject field/subobject|multiple}}}</nowiki>
}}
|<nowiki>{{{for template|Subobject field}}}</nowiki>
}}

'''Required fields:'''

{| class="formtable"
|-
! For category<span style="color:red;"> *</span>: <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">The category this subobject field declaration references.</p>
| <nowiki>{{{field|for_category|property=For category|input type=combobox|values from namespace=Category|autocomplete=on|mandatory=true}}}</nowiki>
|}

'''Optional fields:'''

{| class="formtable"
|-
! Is required: <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">Whether this field is required or optional.</p>
| <nowiki>{{{field|is_required|property=Is required|input type=checkbox|default=no}}}</nowiki>
|-
! Subobject display template: <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">Custom template for rendering an entire subobject section. Set on a Subobject field declaration inside a category to override the default per-subobject table layout — the dispatcher emits a single call to this template (with category= and page= params) in place of the built-in #ask pipeline, so the template can aggregate all subobjects into one table, card grid, timeline, or any layout you want.</p>
| <nowiki>{{{field|has_subobject_display_template|property=Has subobject display template|input type=combobox|values from namespace=Template|autocomplete=on}}}</nowiki>
|}

<nowiki>{{{end template}}}</nowiki>

</includeonly>

Form:Subobject field/composite - Revision history

SemanticSchemas: SemanticSchemas: Auto-generated form