Template:Uses from: Difference between revisions

→‎Discussion: Indicate needed numeral component of template arg name.
(Move '/small' outside the includonly.)
(→‎Discussion: Indicate needed numeral component of template arg name.)
Line 35:
* Avoid using MW categories. Use semantic properties instead. (MW categories have particular behavior when used in semantic queries.)
* Apply the semantic property <tt>'''uses::{{{1}}}'''</tt>
* Accept an undefined number of additional ''named'' arguments as components of that library. (var name might be '''componentcomponentN''') Add a semantic property to the page indicating that it uses {{{1}}}.
** <tt>uses '''{{{1}}}''' component::'''{{{componentcomponent1}}}''', '''{{{component2}}}''', etc...</tt>
* Accept library version as a single named argument. (var name might be '''version''') Tag the transcluding page as using that version of library {{{1}}}.
** <tt>uses '''{{{1}}}''' version:'''{{{version}}}'''</tt>.
* For each {{{componentcomponentN}}} supplied, if any, apply
** <tt>uses '''{{{1}}}''' version '''{{{version}}}''' component::'''{{{componentcomponentN}}}'''</tt>.
** <tt>uses '''{{{1}}}''' component '''{{{componentcomponentN}}}''' version::'''{{{version}}}'''</tt>.
 
The richer the relationships we can define, the more powerful the search options we'll have available.