An diofar eadar na mùthaidhean a rinneadh air "Mòideal:Arguments/doc"

Content deleted Content added
Created page with "{{High-risk|8,000,000+}} This module provides easy processing of arguments passed from #invoke. It is a meta-module, meant for use by other modules, and should not be called..."
 
b Bot: Replace deprecated <source> tag and "enclose" parameter [https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2020-April/002284.html]; cosmetic changes
 
Loidhne 12:
First, you need to load the module. It contains one function, named <code>getArgs</code>.
 
<sourcesyntaxhighlight lang="lua">
local getArgs = require('Module:Arguments').getArgs
</syntaxhighlight>
</source>
 
In the most basic scenario, you can use getArgs inside your main function. The variable <code>args</code> is a table containing the arguments from #invoke. (See below for details.)
 
<sourcesyntaxhighlight lang="lua">
local getArgs = require('Module:Arguments').getArgs
local p = {}
Loidhne 28:
 
return p
</syntaxhighlight>
</source>
 
However, the recommended practice is to use a function just for processing arguments from #invoke. This means that if someone calls your module from another Lua module you don't have to have a frame object available, which improves performance.
 
<sourcesyntaxhighlight lang="lua">
local getArgs = require('Module:Arguments').getArgs
local p = {}
Loidhne 46:
 
return p
</syntaxhighlight>
</source>
 
If you want multiple functions to use the arguments, and you also want them to be accessible from #invoke, you can use a wrapper function.
 
<sourcesyntaxhighlight lang="lua">
local getArgs = require('Module:Arguments').getArgs
 
Loidhne 75:
 
return p
</syntaxhighlight>
</source>
 
=== Options ===
Loidhne 81:
The following options are available. They are explained in the sections below.
 
<sourcesyntaxhighlight lang="lua">
local args = getArgs(frame, {
trim = false,
Loidhne 94:
noOverwrite = true
})
</syntaxhighlight>
</source>
 
=== Trimming and removing blanks ===
Loidhne 104:
However, sometimes you want to use blank arguments as input, and sometimes you want to keep additional whitespace. This can be necessary to convert some templates exactly as they were written. If you want to do this, you can set the <code>trim</code> and <code>removeBlanks</code> arguments to <code>false</code>.
 
<sourcesyntaxhighlight lang="lua">
local args = getArgs(frame, {
trim = false,
removeBlanks = false
})
</syntaxhighlight>
</source>
 
=== Custom formatting of arguments ===
Loidhne 116:
 
Example 1: this function preserves whitespace for the first positional argument, but trims all other arguments and removes all other blank arguments.
<sourcesyntaxhighlight lang="lua">
local args = getArgs(frame, {
valueFunc = function (key, value)
Loidhne 130:
end
})
</syntaxhighlight>
</source>
 
Example 2: this function removes blank arguments and converts all arguments to lower case, but doesn't trim whitespace from positional parameters.
<sourcesyntaxhighlight lang="lua">
local args = getArgs(frame, {
valueFunc = function (key, value)
Loidhne 146:
end
})
</syntaxhighlight>
</source>
 
Note: the above functions will fail if passed input that is not of type <code>string</code> or <code>nil</code>. This might be the case if you use the <code>getArgs</code> function in the main function of your module, and that function is called by another Lua module. In this case, you will need to check the type of your input. This is not a problem if you are using a function specially for arguments from #invoke (i.e. you have <code>p.main</code> and <code>p._main</code> functions, or something similar).
Loidhne 152:
{{cot|Examples 1 and 2 with type checking}}
Example 1:
<sourcesyntaxhighlight lang="lua">
local args = getArgs(frame, {
valueFunc = function (key, value)
Loidhne 169:
end
})
</syntaxhighlight>
</source>
 
Example 2:
<sourcesyntaxhighlight lang="lua">
local args = getArgs(frame, {
valueFunc = function (key, value)
Loidhne 187:
end
})
</syntaxhighlight>
</source>
{{cob}}
 
Loidhne 197:
 
{{cot|Module:ExampleArgs code}}
<sourcesyntaxhighlight lang="lua">
local getArgs = require('Module:Arguments').getArgs
local p = {}
Loidhne 213:
 
return p
</syntaxhighlight>
</source>
{{cob}}
 
Loidhne 291:
Sometimes it can be useful to write new values to the args table. This is possible with the default settings of this module. (However, bear in mind that it is usually better coding style to create a new table with your new values and copy arguments from the args table as needed.)
 
<sourcesyntaxhighlight lang="lua">
args.foo = 'some value'
</syntaxhighlight>
</source>
 
It is possible to alter this behaviour with the <code>readOnly</code> and <code>noOverwrite</code> options. If <code>readOnly</code> is set then it is not possible to write any values to the args table at all. If <code>noOverwrite</code> is set, then it is possible to add new values to the table, but it is not possible to add a value if it would overwrite any arguments that are passed from #invoke.
Loidhne 308:
 
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||
[[CategoryRoinn-seòrsa:Lua metamodules]]
}}</includeonly>