Module:Arguments/doc: Difference between revisions
From Mariopedia, a wiki on Mario, Yoshi, Wario, Donkey Kong, Super Smash Bros., and more!
Jump to navigationJump to search
Content deleted Content added
update transclusion count |
add cat |
||
| Line 8: | Line 8: | ||
* Most features can be customized. |
* Most features can be customized. |
||
== Basic use == |
|||
First, you need to load the module. It contains one function, named <code>getArgs</code>. |
First, you need to load the module. It contains one function, named <code>getArgs</code>. |
||
| Line 276: | Line 276: | ||
|- |
|- |
||
| <code><nowiki>{{ExampleArgs}}</nowiki></code> |
| <code><nowiki>{{ExampleArgs}}</nowiki></code> |
||
| firstInvokeArg |
| firstInvokeArg |
||
|- |
|- |
||
| <code><nowiki>{{ExampleArgs|firstTemplateArg}}</nowiki></code> |
| <code><nowiki>{{ExampleArgs|firstTemplateArg}}</nowiki></code> |
||
| Line 307: | Line 307: | ||
=== Known limitations === |
=== Known limitations === |
||
The use of metatables also has its downsides. Most of the normal Lua table tools won't work properly on the args table, including the <code>#</code> operator, the <code>next()</code> function, and the functions in the table library. If using these is important for your module, you should use your own argument processing function instead of this module. |
The use of metatables also has its downsides. Most of the normal Lua table tools won't work properly on the args table, including the <code>#</code> operator, the <code>next()</code> function, and the functions in the table library. If using these is important for your module, you should use your own argument processing function instead of this module.<includeonly>{{#ifeq:{{SUBPAGENAME}}|sandbox|| |
||
[[CaAtegory:Lua metamodules]] |
|||
}}</includeonly> |
|||
