יחידה:ParamValidator: הבדלים בין גרסאות בדף
בדיקת פרמטרים - גרסה 0.1 |
Typo |
||
| שורה 46: | שורה 46: | ||
"no-templatedata": "[[Category:Parametererror invalid templatedata]]", | "no-templatedata": "[[Category:Parametererror invalid templatedata]]", | ||
"undeclared": "[[Category:Parametererror undecalred]][[Category:parameter undecalred templatename]]<span class='param-error-undeclared'>templatename has undeclared parameters: paramname</span>", | "undeclared": "[[Category:Parametererror undecalred]][[Category:parameter undecalred templatename]]<span class='param-error-undeclared'>templatename has undeclared parameters: paramname</span>", | ||
"missing": "[[Category: | "missing": "[[Category:Parametererror missing]][[Category:Parametererror missing templatename]]<span class='param-error-missing'>templatename misses required parameters: paramname</span>", | ||
"any": "[[Category:Parametererror]]", | "any": "[[Category:Parametererror]]", | ||
"doc-subpage": "Documentation" | "doc-subpage": "Documentation" | ||
גרסה מ־15:18, 19 במרץ 2016
This module is based on idea and original code of User:IKhitron.
the source of this module is in //he.wikipedia.org/wiki/Module:ParamValidator
This module exports two functions: calculateViolations( frame, subpages ), and validateParams( frame ).
calculateViolations( frame, subpages ) finds templatedata, in template page or in one of its subpages in the list, if provided. it returns a table with the violations. if there are none, the table is empty. otherwise it has the structure
{
violation1 = { param1 = value1, param2 = value2 },
violation2 = { ... },
...
}
violation1, violation2 etc. are one of the names of specific violations, as described below. param1, param2 etc. are either the names of parameter passed to the template, or defined in templatedata. value1, value2 etc. are the values passed to the template, or an empty string if no such parameter was passed.
the different violations are as follow:
- no-templatedata
no valid tempaltedata was found in tempalte page, or documentation subpage - undeclared
named parameters with non-empty value, does not exist in templatedata - empty-undeclared
named parameters with empty value, does not exist in templatedata - undeclared-numeric
numeric parameters with non-empty value, does not exist in templatedata - empty-undeclared-numeric
numeric parameters with empty value, does not exist in templatedata - deprecated
parameters with non-empty value, marked as "deprecated" in tempaltedata - empty-deprecated
parameters with empty value, marked as "deprecated" in tempaltedata - empty-required
missing or empty parameter marked as "required" in tempaltedata - incompatible
a non-empty parameter passed to the template, incompatible with the parameter type defined in templatedata
The second function, validateParams( frame ), can be called from the tempalte' using #invoke.
it expects a parameter named "options", which contains the definition of the output. typically, it's used by placing something like so:
<includeonly>{{#invoke:ParamValidator | validateParams | options = {{PV default options}} }}</includeonly>
at the top of the template (be mindful not to add extra spaces and newlines to the template).
the options parameter should be a JSON-encoded string, defining the output, and some special behaviors.
the example above assumes that a wiki page named Template:PV default options exists, and contains valid JSON string.
for each of the violations defined above, "options" may define an output string, so basically, "options" looks like so:
{
violation1: outputstring1,
violation2: outputstring2,
.... ,
behavior1: some value,
....
}
not all violations have to be defined. a violation not defined in "options" will be ignored.
when invoked, it extract "subpages" from the options parameter, and calls:
- calculateViolations( frame, subpages )
if the returned table is empty, no violation were found, and an empty string is returned and nothing else happens.
otherwise, for each of the violations, i.e., the keys of the returned table, when "options" contains this key, the corresonding value is appended to the output.
some further processing is done:
- several tokens are replaced with calculated values. these are described below.
- some "meta" violations are calculated: when any none-ignored violation occured, the "any" meta-violation is added to the output in the same way, i.e. the string keyed by "any" in the options is appended to output with appropriate substitutions. similarly, "multiple" meta-violation is created when more than one type of non-ignored violations occured.
- if the output is not empty, a prefix and suffix strings are prepended and appended to it.
these are the tokens and the replacement.
- templatename
full template name, including namespace. - tname_naked
template name without namespace. - paramname
comma-separated list of parameters - paramandvalue
is replaced by comma-separated list of "name: value" pairs of parameters and values
the first two are applied to the whole output, including the suffux and prefix, and the rest are applied to the individual violations, each with its own list of offending parameters and values.
the rest of the if the value of some keys is null, this error condition will be ignored, and not counted when calculating "any" and "multiple" conditions.
some other optional fields can be passed via options:
- doc-subpage
can be either a string, or a list (in square bracktes) of strings, indicating subpages of the template that may contain templatedata. - ignore
list of patterns. any parameter whose name matches any pattern, will not considered in violation of any of the rules. - skip-empty-numeric
if a quoted number, the module will ignore non-declared empty numeric parameters up to this number - wrapper-prefix
openning wrapper element of outpot (defaults to<div class = 'paramvalidator-wrapper'>) - wrapper-suffix
closing wrapper element of output (defaults to "</div>")
additional option parameters, named options1, options2, etc. can be passed. any entry defined in these options will override the previous value. a typical use may be like so:
typically, this JSON structure will be placed in a separate template, and retrieved for the module-use as shown above.
<includeonly>{{#invoke:ParamValidator | validateParams | options = {{PV default options}} | options1 = {"key":"value"} }}</includeonly>
"key" can override any of the options fields described above.
--[[
this unit contains a single function.
it gets 2 optional parameters:
base = options base name, for the inbuilt options. if not passed, "default" is assumed.
ATM, the only other viable value is "quiet" (without quotes). this is useful when complete substitution of all the outputs is desired.
options = json-coded string that describes the desired output for each error condition, and some more site-specific settings,
such as the default "Documentation" subpage, so the function can try to look for tempaltedata in the correct subpages.
there are 4 error conditions, and a the options define the desired output for each.
if no output is desired for specific option, give the appropriate key empty string value.
the 4 error conditions are:
* "no-templatedata": this means no valid tempaltedata was found
* "undeclared": parameters passed to the template which do not exist in templatedata
* "missing": parameters marked as "required" in tempaltedata are not passed
* "any": any of the above conditions is true.
for each condition that evaluates to true, the value of the corresponding options field is used to add to the output of the function.
before appending this value to the output, 2 substitutions occur: the tokens "templatename" and "paramname" in the value are
substituted with the actual template name, and a comma-joined list of the undeclared or missing parameters, where relevant.
there is one more useful option:
* "doc-subpage": use this field to tell what is the default "Documentation" subpage on your wiki. this enable the system to
look for tempalatedata in the appropriate subpage.
usage:
place
<includeonly>{{#invoke:ParamValidator | validateParams }}</includeonly>
at the very bigining of the tempalate (not mandatory - it can be in any part of the template, but it's recommended).
<includeonly>{{#invoke:ParamValidator | validateParams | base = quiet }}</includeonly>
will use the "quiet" inbuilt option. the default behavior in this case is to only emit a html comment to the page if any error exists.
you can pass your own options. these options will be applied above the selected (or default) inbuilt.
the options value is supplied as a json-encoded string. it is recommended to create one or two tempaltes that will return
the desired options (in valid json format) so the use will be like so:
<
includeonly>{{#invoke:ParamValidator | validateParams | options = {{validator-options}} }}</includeonly>
use the "default" option as template for the template to be used on your site.
]]
local inbuilt_options = {
default = [=[
{
"no-templatedata": "[[Category:Parametererror invalid templatedata]]",
"undeclared": "[[Category:Parametererror undecalred]][[Category:parameter undecalred templatename]]<span class='param-error-undeclared'>templatename has undeclared parameters: paramname</span>",
"missing": "[[Category:Parametererror missing]][[Category:Parametererror missing templatename]]<span class='param-error-missing'>templatename misses required parameters: paramname</span>",
"any": "[[Category:Parametererror]]",
"doc-subpage": "Documentation"
}
]=]
,
-- allow for more inbuilt settings.
quiet = [[
{ "any": "<!-- Some template parameters errors exist, for tempplate templatename -->" }
]]
}
function extract_options( frame )
local options
local args = frame.args
local base = args.base or 'default'
local options = mw.text.jsonDecode( args.options or '{}' )
local base_options = mw.text.jsonDecode( inbuilt_options[base] or '{}' )
for k, v in pairs( base_options ) do
options[k] = options[k] or v
end
return options
end
function build_namelist( options, template_name )
if options and options['doc-subpage'] then
return { template_name, template_name .. '/' .. options['doc-subpage'] }
end
return template_name
end
function validateParams( frame )
local options = extract_options( frame )
local t_frame = frame:gatParent()
local t_args = t_frame.args
local template_name = t_frame:getTitle()
local templatedata = require( 'Module:ReadTd' ).readTemplateData( build_namelist ( options, template_name ) )
local report = ''
local replace_macros = function( s, paramnames )
local processed = mw.ustring.gsub( s, 'templatename', template_name )
if paramname then
processed = mw.ustring.gsub( processed, 'paramname', paramnames )
end
return processed
end
local report_params = function( key, param_names )
if options[key] then
report = report .. replace_macros( options[key], param_names )
end
end
if not templatedata then
report_param( notd_keys )
report_param( general_keys )
return report
end
local td_p = templatedata.params
local undeclared, missing = {}, {}
for p_name, _ in pairs( t_args ) do
if not td_p[p_name] then
table.insert( undeclared, p_name )
end
end
for p_name, param in pairs( td_p ) do
if param.required and not t_args[p_name] then
table.insert( missing, p_name )
end
end
if #missing ~= 0 then
report_params( 'missing', table.concat( missing, ', ' ) )
end
if #undecalred ~= 0 then
report_params( 'undeclared', table.concat( undecalred, ', ' ) )
end
if #missing + #undecalred ~= 0 then
report_params( 'any' )
end
return report
end
return {
['validateparams'] = validateParams
}