Module:Category handler/doc: Difference between revisions

Jump to navigation Jump to search
>Tomoneill
(copy from https://en.wikipedia.org/w/index.php?title=Module:Category_handler/doc&oldid=874163486)
 
>Nickps
Line 1: Line 1:
{{high-use|4486247|all-pages = yes}}
{{Used in system}}
{{Used in system}}
{{Module rating|p}}
{{Module rating|p}}
{{Lua|Module:Category handler/data|Module:Category handler/shared|Module:Category handler/blacklist|Module:Yesno|Module:Arguments}}


This module implements the {{tl|category handler}} template. The category handler template helps other templates to automate both categorization and [[Wikipedia:Category suppression|category suppression]]. For information about using the category handler template in other templates, please see the '''[[Template:Category handler|template documentation]]'''. Keep reading for information about using the category handler module in other Lua modules, or for information on exporting this module to other wikis.
This module implements the {{tl|category handler}} template. The category handler template helps other templates to automate both categorization and [[Wikipedia:Category suppression|category suppression]]. For information about using the category handler template in other templates, please see the '''[[Template:Category handler|template documentation]]'''. Keep reading for information about using the category handler module in other Lua modules, or for information on exporting this module to other wikis.
Line 9: Line 9:
=== When not to use this module ===
=== When not to use this module ===


For cases where a module only needs to categorise in one of the namespaces main (articles), file (images) or category, then using this module is overkill. Instead, you can simply get a title object using [[rev:https://www.mediawiki.org/wiki/Extension:Scribunto/Lua reference manual#mw.title.getCurrentTitle#mw.title.getCurrentTitle|mw.title.getCurrentTitle]] and check the <code>nsText</code> field. For example:
For cases where a module only needs to categorise in one of the namespaces main (articles), file (images) or category, then using this module is overkill. Instead, you can simply get a title object using [[mw:Extension:Scribunto/Lua reference manual#mw.title.getCurrentTitle|mw.title.getCurrentTitle]] and check the <code>nsText</code> field. For example:
<source lang="lua">
<syntaxhighlight lang="lua">
local title = mw.title.getCurrentTitle()
local title = mw.title.getCurrentTitle()
if title.nsText == 'File' then
if title.nsText == 'File' then
     -- do something
     -- do something
end
end
</source>
</syntaxhighlight>
However, if your module needs to categorize in any other namespace, then we recommend you use this module, since it provides proper category suppression and makes it easy to select how to categorize in the different namespaces.
However, if your module needs to categorize in any other namespace, then we recommend you use this module, since it provides proper category suppression and makes it easy to select how to categorize in the different namespaces.


Line 35: Line 35:
This module takes two or more parameters. Here's an example using a hello world program:
This module takes two or more parameters. Here's an example using a hello world program:


<source lang="lua">
<syntaxhighlight lang="lua">
p = {}
p = {}
local categoryHandler = require( 'Module:Category handler' ).main
local categoryHandler = require( 'Module:Category handler' ).main
 
function p.main( frame )
function p.main( frame )
     local result = 'Hello world!'
     local result = 'Hello world!'
Line 48: Line 48:
     return result .. category
     return result .. category
end
end
 
return p
return p
</source>
</syntaxhighlight>


The above example uses the default settings for the category handler module. That means the example module will categorize on pages in the following namespaces:  
The above example uses the default settings for the category handler module. That means the example module will categorize on pages in the following namespaces:
:'''main''', '''file''', '''help''', '''category''', '''portal''' and '''book'''
:'''main''', '''file''', '''help''', '''category''', '''portal''' and '''book'''
But it will ''not'' categorize in any other namespaces, e.g.:
But it will ''not'' categorize in any other namespaces, e.g.:
Line 59: Line 59:
And it will ''not'' categorize on blacklisted pages. (See section [[#Blacklist|blacklist]] below.)
And it will ''not'' categorize on blacklisted pages. (See section [[#Blacklist|blacklist]] below.)


The reason the category handler module does not categorize in some of the namespaces is that in those namespaces most modules and templates are just demonstrated or listed, not used. Thus most modules and templates should not categorize in those namespaces.  
The reason the category handler module does not categorize in some of the namespaces is that in those namespaces most modules and templates are just demonstrated or listed, not used. Thus most modules and templates should not categorize in those namespaces.


Any module or template that is meant for one or more of the namespaces where this module categorizes can use the basic syntax as shown above.
Any module or template that is meant for one or more of the namespaces where this module categorizes can use the basic syntax as shown above.
Line 67: Line 67:
This module takes one or more parameters named after the different page types as listed in section [[#Namespaces|namespaces]] above. By using those parameters you can specify exactly in which namespaces your template should categorize. Like this:
This module takes one or more parameters named after the different page types as listed in section [[#Namespaces|namespaces]] above. By using those parameters you can specify exactly in which namespaces your template should categorize. Like this:


<source lang="lua">
<syntaxhighlight lang="lua">
p = {}
p = {}
local categoryHandler = require( 'Module:Category handler' ).main
local categoryHandler = require( 'Module:Category handler' ).main
 
function p.main( frame )
function p.main( frame )
     local result = 'This is a module meant for articles and talk pages.'
     local result = 'This is a module meant for articles and talk pages.'
Line 81: Line 81:
     return result .. category
     return result .. category
end
end
 
return p
return p
</source>
</syntaxhighlight>


The above module will only categorize in main and talk space. But it will not categorize on /archive pages since they are blacklisted. (See section [[#Blacklist|blacklist]] below.) And if you need to demonstrate (discuss) the module on a talkpage, then you can feed "<code>nocat='true'</code>" to prevent that template from categorizing. (See section [[#Nocat|nocat]] below.) Like this:
The above module will only categorize in main and talk space. But it will not categorize on /archive pages since they are blacklisted. (See section [[#Blacklist|blacklist]] below.) And if you need to demonstrate (discuss) the module on a talkpage, then you can feed "<code>nocat='true'</code>" to prevent that template from categorizing. (See section [[#Nocat|nocat]] below.) Like this:
Line 97: Line 97:
Sometimes we want to use the same category in several namespaces, then do like this:
Sometimes we want to use the same category in several namespaces, then do like this:


<source lang="lua">
<syntaxhighlight lang="lua">
p = {}
p = {}
local categoryHandler = require( 'Module:Category handler' ).main
local categoryHandler = require( 'Module:Category handler' ).main
 
function p.main( frame )
function p.main( frame )
     local result = 'This is a module used in several namespaces.'
     local result = 'This is a module used in several namespaces.'
Line 115: Line 115:
     return result .. category
     return result .. category
end
end
 
return p
return p
</source>
</syntaxhighlight>


In the above example we use a numbered parameter to feed one of the categories, and then we tell this module to use that numbered parameter for both the help and user space.
In the above example we use a numbered parameter to feed one of the categories, and then we tell this module to use that numbered parameter for both the help and user space.
Line 129: Line 129:
The category handler module also has a parameter called '''all'''. It works like this:
The category handler module also has a parameter called '''all'''. It works like this:


<source lang="lua">
<syntaxhighlight lang="lua">
p = {}
p = {}
local categoryHandler = require( 'Module:Category handler' ).main
local categoryHandler = require( 'Module:Category handler' ).main
 
function p.main( frame )
function p.main( frame )
     local result = 'This is a module used in all namespaces.'
     local result = 'This is a module used in all namespaces.'
Line 142: Line 142:
     return result .. category
     return result .. category
end
end
 
return p
return p
</source>
</syntaxhighlight>


The above example will categorize in all namespaces, but not on blacklisted pages. If you want to demonstrate that module on a page, then use "<code>nocat=true</code>" to prevent the template from categorizing.  
The above example will categorize in all namespaces, but not on blacklisted pages. If you want to demonstrate that module on a page, then use "<code>nocat=true</code>" to prevent the template from categorizing.  
Line 152: Line 152:
The all parameter can also be combined with the rest of the parameters. Like this:
The all parameter can also be combined with the rest of the parameters. Like this:


<source lang="lua">
<syntaxhighlight lang="lua">
p = {}
p = {}
local categoryHandler = require( 'Module:Category handler' ).main
local categoryHandler = require( 'Module:Category handler' ).main
 
function p.main( frame )
function p.main( frame )
     local result = 'This is a module used in all namespaces.'
     local result = 'This is a module used in all namespaces.'
Line 167: Line 167:
     return result .. category
     return result .. category
end
end
 
return p
return p
</source>
</syntaxhighlight>


If the above module is placed on an article, then it will add the categories "Somecat1" and "Somecat2". But on all other types of pages it will instead add "Somecat1" and "Somecat3". As the example shows, the all parameter works independently of the rest of the parameters.
If the above module is placed on an article, then it will add the categories "Somecat1" and "Somecat2". But on all other types of pages it will instead add "Somecat1" and "Somecat3". As the example shows, the all parameter works independently of the rest of the parameters.
Line 177: Line 177:
The category handler module understands the '''subpage''' parameter. Like this:
The category handler module understands the '''subpage''' parameter. Like this:


<source lang="lua">
<syntaxhighlight lang="lua">
p = {}
p = {}
local categoryHandler = require( 'Module:Category handler' ).main
local categoryHandler = require( 'Module:Category handler' ).main
 
function p.main( frame )
function p.main( frame )
     local result = 'This is a module used in all namespaces.'
     local result = 'This is a module used in all namespaces.'
Line 191: Line 191:
     return result .. category
     return result .. category
end
end
 
return p
return p
</source>
</syntaxhighlight>


If "<code>subpage='no'</code>" then this template will ''not'' categorize on subpages. For the rare occasion you ''only'' want to categorize on subpages, then use "<code>subpage='only'</code>". If '''subpage''' is empty or undefined then this template categorizes both on basepages and on subpages.
If "<code>subpage='no'</code>" then this template will ''not'' categorize on subpages. For the rare occasion you ''only'' want to categorize on subpages, then use "<code>subpage='only'</code>". If '''subpage''' is empty or undefined then this template categorizes both on basepages and on subpages.
Line 210: Line 210:


* If "<code>nocat = true</code>" then this template does ''not'' categorize.
* If "<code>nocat = true</code>" then this template does ''not'' categorize.
* If '''nocat''' is <code>nil</code> then this template categorizes as usual.  
* If '''nocat''' is <code>nil</code> then this template categorizes as usual.
* If "<code>nocat = false</code>" this template categorizes even when on blacklisted pages. (See section [[#Blacklist|blacklist]] above.)
* If "<code>nocat = false</code>" this template categorizes even when on blacklisted pages. (See section [[#Blacklist|blacklist]] above.)
* The nocat parameter also accepts aliases for <code>true</code> and <code>false</code> as defined by [[Module:Yesno]], e.g. "yes", "y", "true", and 1 for <code>true</code>, and "no", "n", "false", and 0 for <code>false</code>.
* The nocat parameter also accepts aliases for <code>true</code> and <code>false</code> as defined by [[Module:Yesno]], e.g. "yes", "y", "true", and 1 for <code>true</code>, and "no", "n", "false", and 0 for <code>false</code>.
Line 220: Line 220:
For backwards compatibility this module also understands the '''categories''' parameter. It works the same as '''nocat'''. Like this:
For backwards compatibility this module also understands the '''categories''' parameter. It works the same as '''nocat'''. Like this:


* If "<code>categories = false</code>" then this template does ''not'' categorize.  
* If "<code>categories = false</code>" then this template does ''not'' categorize.
* If '''categories''' is empty or undefined then this template categorizes as usual.  
* If '''categories''' is empty or undefined then this template categorizes as usual.
* If "<code>categories = true</code>" this template categorizes even when on blacklisted pages.
* If "<code>categories = true</code>" this template categorizes even when on blacklisted pages.
* The categories parameter also accepts aliases for <code>true</code> and <code>false</code> as defined by [[Module:Yesno]], e.g. "yes", "y", "true", and 1 for <code>true</code>, and "no", "n", "false", and 0 for <code>false</code>.
* The categories parameter also accepts aliases for <code>true</code> and <code>false</code> as defined by [[Module:Yesno]], e.g. "yes", "y", "true", and 1 for <code>true</code>, and "no", "n", "false", and 0 for <code>false</code>.
Line 237: Line 237:
Besides from categories, you can feed anything else to this module, for instance some text. Like this:
Besides from categories, you can feed anything else to this module, for instance some text. Like this:


<source lang="lua">
<syntaxhighlight lang="lua">
p = {}
p = {}
local categoryHandler = require( 'Module:Category handler' ).main
local categoryHandler = require( 'Module:Category handler' ).main
Line 253: Line 253:


return p
return p
</source>
</syntaxhighlight>


When the module code above is used on anything other than a talk page, it will look like this:
When the module code above is used on anything other than a talk page, it will look like this:
Line 269: Line 269:
For testing and demonstration purposes this module can take a parameter named '''page'''. Like this:
For testing and demonstration purposes this module can take a parameter named '''page'''. Like this:


<source lang="lua">
<syntaxhighlight lang="lua">
p = {}
p = {}
local categoryHandler = require( 'Module:Category handler' ).main
local categoryHandler = require( 'Module:Category handler' ).main
 
function p.main( frame )
function p.main( frame )
     local category = categoryHandler{
     local category = categoryHandler{
Line 282: Line 282:
     return category
     return category
end
end
 
return p
return p
</source>
</syntaxhighlight>


In the above code we on purpose left out the brackets around the category names so we see the output on the page. No matter on what kind of page the code above is used it will return this:
In the above code we on purpose left out the brackets around the category names so we see the output on the page. No matter on what kind of page the code above is used it will return this:
Line 291: Line 291:
| main = Category:Some cat
| main = Category:Some cat
| talk = Category:Talk cat
| talk = Category:Talk cat
| nocat = {{{nocat|}}}   <!--So "nocat=true/false" works-->
| nocat = {{{nocat|}}} <!--So "nocat=true/false" works-->
| page = User talk:Example
| page = User talk:Example
}}
}}
Line 301: Line 301:
You can make it so your module also understands the '''page''' parameter. That means you can test how your template will categorize on different pages, without having to actually edit those pages. Then do like this:
You can make it so your module also understands the '''page''' parameter. That means you can test how your template will categorize on different pages, without having to actually edit those pages. Then do like this:


<source lang="lua">
<syntaxhighlight lang="lua">
p = {}
p = {}
local categoryHandler = require( 'Module:Category handler' ).main
local categoryHandler = require( 'Module:Category handler' ).main
Line 316: Line 316:


return p
return p
</source>
</syntaxhighlight>


=== Parameters ===
=== Parameters ===
Line 332: Line 332:
* categories = frame.args.categories / false / true / 'no' / 'yes' / 'n' / 'y' / 'false' / 'true' / 0 / 1
* categories = frame.args.categories / false / true / 'no' / 'yes' / 'n' / 'y' / 'false' / 'true' / 0 / 1
* category2 = frame.args.category or '¬' / 'no' / 'not defined' / '¬' / 'yes'
* category2 = frame.args.category or '¬' / 'no' / 'not defined' / '¬' / 'yes'
* page = frame.args.page / 'User:Example'
* page = frame.args.page / 'User:Example'


Note that empty values to the "main" ... "other" parameters have special meaning (see examples above). The "all" parameter doesn't understand numbered parameters, since there should never be a need for that.
Note that empty values to the "main" ... "other" parameters have special meaning (see examples above). The "all" parameter doesn't understand numbered parameters, since there should never be a need for that.
Line 346: Line 346:
* [[Wikipedia:WikiProject Category Suppression]] – The WikiProject.
* [[Wikipedia:WikiProject Category Suppression]] – The WikiProject.
* [[Wikipedia:Namespace]] – Lists all the namespaces.
* [[Wikipedia:Namespace]] – Lists all the namespaces.
<noinclude>
[[Category:Module documentation pages]]
</noinclude>
Anonymous user

Navigation menu