https://wiki.iccup.org/index.php?action=history&feed=atom&title=%D0%9C%D0%BE%D0%B4%D1%83%D0%BB%D1%8C%3AClass%2FdocМодуль:Class/doc - История изменений2026-05-31T16:53:11ZИстория изменений этой страницы в викиMediaWiki 1.42.3https://wiki.iccup.org/index.php?title=%D0%9C%D0%BE%D0%B4%D1%83%D0%BB%D1%8C:Class/doc&diff=202&oldid=prevDarkMuse: Новая страница: «Enables equal treatment of Lua and wikicode users for modules. Using this module means you will no longer need to have two different entry points for each function—both Lua and wikicode can call the same function. ==Usage== Using this module is straightforward. Here's an example: <pre> local Class = require('Module:Class') <!--- Add the import local Cool = Class.new() <!--- Create a class function Cool.doCoolStuff...»2024-09-02T17:43:17Z<p>Новая страница: «Enables equal treatment of Lua and wikicode users for modules. Using this module means you will no longer need to have two different entry points for each function—both Lua and wikicode can call the same function. ==Usage== Using this module is straightforward. Here's an example: <pre> local Class = require('Module:Class') <!--- Add the import local Cool = Class.new() <!--- Create a class function Cool.doCoolStuff...»</p>
<p><b>Новая страница</b></p><div>Enables equal treatment of Lua and wikicode users for modules. Using this module means you will no longer need to have two different entry points for each function—both Lua and wikicode can call the same function.<br />
==Usage== Using this module is straightforward. Here's an example:<br />
<pre> local Class = require('Module:Class') <!--- Add the import local Cool = Class.new() <!--- Create a class function Cool.doCoolStuff(a, b) <!--- Note the colon symbol! return a + b end return Cool.export() <!--- Export the table </pre><br />
Now, <code>doCoolStuff</code> can be called from both Lua and wikicode with the same arguments.<br />
To illustrate, you can use <code>Cool<br />
(2, 3)</code> in Lua, and also use <code><nowiki>{{#invoke<br />
|doCoolStuff|2|3}}</nowiki></code> in wikicode, and both will return 5.<br />
===Named Arguments=== When named arguments are provided, there's a slight change. Named arguments are supplied as a Lua table and are always the first argument. Here's how:<br />
<pre> local Class = require('Module:Class') <!--- Add the import local Cool = Class.new() <!--- Create a class function Cool.doCoolStuff(args, a, b) <!--- Named args are now the first argument! return a + b + args.c end return Cool.export() <!--- Export the table </pre><br />
You can now call <code>Cool<br />
({c = 5}, 2, 3)</code> in Lua, and similarly use <code><nowiki>{{#invoke<br />
|doCoolStuff|2|3|c=5}}</nowiki></code> in wikicode, and both will return 10.<br />
===Advanced Usage=== Module:Class supports advanced usage scenarios via the export function's options parameter. These options are passed directly to the Module:Arguments, allowing you to specify features such as frame inheritance, trimming, and more. For more details, refer to iCCup's Module<br />
documentation.<br />
==API== {{ApiDocStart|Class|link=Module<br />
}} {{ApiDoc|export|params=class: table, options: table|description=Adjusts the provided table so that its public functions (those not prefixed with an underscore) are usable from both Lua and wikicode, and returns the modified table. Note: Avoid creating underscored versions of your public methods—use distinct names. For instance, don't use both copy() and _copy() in the same module. The options parameter allows passing arguments to Module:Arguments's getArgs method.|returns=class}} {{ApiDoc|new|params=base: class, init: function|description=Creates a new class by setting the proper metadata. If a base class is provided, it will be used as the base. An optional init function can act as a constructor. If only init is provided, it functions independently.|returns=class}} {{ApiDocEnd}}</div>DarkMuse