Banri: Created page with "{{Documentation}} Uses Module:DPLlua/Helper to make it possible to include all parameters of a template while maintaining good performance. {{Helper module|name=DPLlua |..."

2021-03-24T01:56:22Z

Created page with "{{Documentation}} Uses Module:DPLlua/Helper to make it possible to include all parameters of a template while maintaining good performance. {{Helper module|name=DPLlua |..."

New page

{{Documentation}}
Uses [[Module:DPLlua/Helper]] to make it possible to include all parameters of a template while maintaining good performance.

{{Helper module|name=DPLlua
|fname1 = ask( ... )
|ftype1 = tables
|fuse1 = <code>ask</code> takes a series of tables each containing the settings for a DPL query; it will return the same number of result tables as input tables. All formatting settings are stripped from the config. If the config does not contains <code>include</code>, the result will be a simple list of page names.
<pre>
{
<pagename#1>,
<pagename#2>,
<pagename#3>,
}
</pre>
A query with an <code>include</code> of the form <code>include = '{template#1}:1:2:param1:param2, {template#2}:3:param1, %0'</code> will give a result like
<pre>
{
['include'] = {
['template#1'] = {
[1] = val#1,
[2] = val#2,
['param1'] = val#3,
['param2'] = val#4,
},
['template#2'] = {
[3] = val#5,
['param1'] = val#6,
},
['%0'] = val#7
},
['title'] = <pagename>
}
</pre>
You can also do <code>include = '{some template}'</code> which will include all parameters of that template in their unexpanded form (templates are not expanded but some content in parser tags is placed in strip markers).

If a template appears multiple times on the same page then <code>val#1</code> of the above example will be be a table like <code>{val#1 of template 1, val#1 of template 2, ...}</code>, etc.

If the config value <code>count</code> is larger than 500 it will automatically generate multiple DPL queries with offsets and their outputs will be combined in the returned result.

The output contains a <code>time</code> field so you don't need to use <code>%DPLTIME%</code>.

If the DPL throws an error it will be available in the <code>error</code> field of the output.

Differences with normal DPL:
* All formatting options are ignored
* Using <code>include = '{template}'</code> will include all the arguments of that template instead of expanding the template
* The parameter <code>count</code> can go higher than 500
* When the value of a parameter is a table it will be expanded into multiple lines. E.g. doing <code>notcategory = {val#1, val#2}</code> will expand into
<pre>
|notcategory = val#1
|notcategory = val#2
</pre>

Note, if you include a whole template (e.g. <code>include = '{some template}'</code>), content inside strip markers (not nowiki) can't be cleaned up inside lua so pipe characters (<code>|</code>) will be replaced with <code>§</code> characters and the <code>{</code> and <code>}</code> characters are replaced by <code>❴</code> (U+2774) and <code>❵</code> (U+2775). Use <code>include = '{some template}, {some template}:1:2:3'</code> instead for the problem parameters.
}}

Module:DPLlua/doc - Revision history

Banri: Created page with "{{Documentation}} Uses Module:DPLlua/Helper to make it possible to include all parameters of a template while maintaining good performance. {{Helper module|name=DPLlua |..."