Template:RootFieldType: Difference between revisions

Template page
Move bolding here instead of Table ComponentFields
Add way to handle nested direct types
 
(One intermediate revision by the same user not shown)
Line 10: Line 10:
|RawOutput`1=''raw output'' of '''{{{2}}}'''
|RawOutput`1=''raw output'' of '''{{{2}}}'''
|SyncArray`1=''array'' of '''{{{2}}}'''
|SyncArray`1=''array'' of '''{{{2}}}'''
|''direct'' '''[[Type:{{{1}}}|{{{1}}}]]{{#if:{{{2}}}|&lt;{{{2}}}&gt;}}'''}}</onlyinclude></includeonly>
|(nested)=''direct'' '''{{{2}}}'''
|''direct'' '''[[Type:{{{1}}}|{{{1}}}]]{{#if:{{{2|}}}|&lt;{{{2}}}&gt;}}'''}}</onlyinclude></includeonly>


This type is used by component field tables to "hide" the real field type. We don't want to explain to people that 99% of field types are actually <code>Sync`1</code> or something, so common types get hidden or turned into something nice. Cases where the real field type is shown are listed as "direct" as an unambiguous fallback.
This type is used by component field tables to "hide" the real field type. We don't want to explain to people that 99% of field types are actually <code>Sync`1</code> or something, so common types get hidden or turned into something nice. Cases where the real field type is shown are listed as "direct" as an unambiguous fallback.

Latest revision as of 21:59, 3 March 2024


This type is used by component field tables to "hide" the real field type. We don't want to explain to people that 99% of field types are actually Sync`1 or something, so common types get hidden or turned into something nice. Cases where the real field type is shown are listed as "direct" as an unambiguous fallback.

The first parameter is the real field type, without generic args. So like Sync`1. The second argument is the generic contents, comma separated.

Float

list of Float

list of Sync`1<Float>

direct IKSolverVR

direct FooBar`1<Float>

direct FooBar`2<Float, Float>