Xenharmonic Wiki

User:Ganaram inukshuk/Provisional style guide for Lua: Difference between revisions

← Older edit
VisualWikitext
Ganaram inukshuk (talk | contribs)
autopatrolled, emailconfirmed
6,211 edits
No edit summary
Ganaram inukshuk (talk | contribs)
autopatrolled, emailconfirmed
6,211 edits
No edit summary
 
(32 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Parts of it are adapted to follow editing on the wiki.
The following style guide is a personal, provisional guide adapted from the LuaRocks style guide: https://github.com/luarocks/lua-style-guide
== Lua style ==


The following style guide is a provisional guide adapted from the LuaRocks style guide: https://github.com/luarocks/lua-style-guide
Parts of it are adapted for use on the wiki, with details on specific conventions. If a specific convention is missing, fall back to that described in the Luarocks style guide.
 
== Provisional additions for version 2 ==
Consistency with param names, including spelling:
 
* Define all param names at the module level, not the template level
* Use snake_case for all param names throughout; anything remotely close to snake_case is normalized to snake_case
* "debug" and "nocat" are reserved for toggling categories; the use of "debug" this way has already been the standard
 
== Preliminaries ==


=== Indentation and formatting ===
=== Indentation and formatting ===
Use the default as specified by the in-browser Lua editor.
The in-browser Lua editor uses tabs for indenting, which equates to 4 spaces.


=== Documentation ===
=== Naming and declaring variables ===
''to be determined''


=== Variable names ===
Variable names should be short and descriptive, written in <code>snake_case</code>. Exceptions to this include counter variables, like with <code>i</code> in for loops. Boolean variables are prefixed with <code>is_</code> or <code>has_</code> wherever possible. Constants are named using <code>TRAIN_CASE</code>.
Same as LuaRocks style guide.


=== Tables ===
All variable declarations should start with <code>local</code>.
Same as LuaRocks style guide.


=== Strings ===
=== Strings ===
Same as LuaRocks style guide.


Do not escape double-quotes when a string can be enclosed in single-quotes instead. Only escape double-quotes when a string contains both single and double quotes.
Strings are enclosed in double quotes <code>" "</code>. If a string contains double quotes, do not escape them while enclosing the string in double quotes, as this reduces readability; instead, enclose the string in single quotes <code>' '</code>. Escape characters for quotes should only be used if the string contains both single and double quotes.
 
'''Preferred'''
<syntaxhighlight lang="lua">local sentence = "That's his cheese quesadilla!"
local quotation = "And he said to me, \"One man's trash is another man's treasure.\""
</syntaxhighlight>
 
'''Avoid'''
<syntaxhighlight lang="lua">local formatting = "padding: 0.25em 0.5em; border: 1px solid white;\" colspan="2\" | "
</syntaxhighlight>


=== Line lengths ===
=== Line lengths ===
''to be determined''


=== Function declaration syntax ===
The 80-column limit should be observed wherever possible for both comments and code, except for cases where strings, inline comments, or function calls are too long.
Same as LuaRocks style guide
 
<syntaxhighlight lang="lua">
local function navbox_title()
if not title then return "" end
local has_navbar = name ~= nil
 
return "|-\n" ..
'! style="text-align: center; background-color: #eaecf0; white-space: nowrap; margin: 0em 4em 0em 4em;' ..
'padding: 0.25em 0.5em; border: 1px solid white;" colspan="2" | ' ..
'<span style="display: inline-block; float: left; text-align: left; font-weight: normal; font-style: normal; min-width: 4em; padding: 0px; margin: 0px;">' ..
(has_navbar and navbar(name, "mini", "") or "") .. '</span>' ..
'<span style="font-size: 1.05em;">' .. title .. '</span>' ..
(is_collapsible and '' or '<span style="display: inline-block; float: right; font-size: 0.8em; width: 5em;">&nbsp;</span>')
end
</syntaxhighlight>
 
=== Naming, declaring, and calling functions ===
 
As with variables, functions are named using <code>snake_case</code>. Functions that return a boolean variable are prefixed with <code>is_</code> or <code>has_</code>.
 
''tbd''
 
=== Comments in code ===
 
Well-commented code should speak for itself. Self-documenting code can only go so far, so comments should be used to briefly describe what the function does. If a module has several types of functions, comments can also be used as section separators.
 
TODOs are allowed in comments. Separating TODOs into the module's documentation page makes code harder to maintain.
 
=== Commented-out code ===
 
Only block comments <code> --[[  ]]-- </code> should only be used for commented-out code. This can be hard to do if a string contains a <code>]]</code>, so <code>--</code> may be used instead.
 
== Conventions for Lua modules ==
 
=== Boilerplate code ===
Alphabetize dependencies, except for p, which goes last and separated by a line. Equals signs may be lined up.
 
'''Preferred order'''<syntaxhighlight lang="lua" line="1">local mos    = require("Module:MOS")
local rat    = require("Module:Rational")
local utils  = require("Module:Utils")
 
local p = {}</syntaxhighlight>'''Avoid'''<syntaxhighlight lang="lua" line="1">
local p = {}
local mos    = require("Module:MOS")
local rat    = require("Module:Rational")
local utils  = require("Module:Utils")
</syntaxhighlight><syntaxhighlight lang="lua" line="1">
local p = {}
local rat = require("Module:Rational")
local mos = require("Module:MOS")
local utils = require("Module:Utils")
</syntaxhighlight>
 
=== Placement of comments and TODO comments ===
Comments may be placed before modules as a preface, inline with modules to describe what each module does, and after the boilerplate code as a descripion. TODO comments should be placed before the code's description for ease of access.
 
TODO comments should not be confused with the todo categories, nor should such code-based TODOs ever be placed in [[Template:Todo]]; placing such tasks in the template makes it harder to maintain code and mixes up code-based tasks with wiki-based tasks.<syntaxhighlight lang="lua" line="1">-- Preface goes here
local mos    = require("Module:MOS")      -- For mos scale functions
local rat    = require("Module:Rational")  -- For JI ratio calculations
local utils  = require("Module:Utils")    -- Contains the gcd function
 
local p = {}
 
-- TODO goes here, if any
 
-- Description goes here</syntaxhighlight>
=== Use of functions ===
 
===== Modules that implement templates =====
Modules that implement templates should consist of at least two functions: a "main" function prefixed with an underscore, and a wrapper function of the same name but without an underscore.
 
The use of a wrapper and "main" function allows for a module to be used directly in another module or indirectly through its corresponding template. A module should only provide '''one''' wrapper for '''one''' template. If the "main" function is short enough, its code may be merged with the wrapper function.
 
A tester function may be added for testing purposes, which is itself a wrapper that also calls the "main" function. This allows it to be tested using the in-browser console by calling mw.logObject(p.tester()). Tester functions may be removed if the "main" function is determined to be functional under expected conditions.<syntaxhighlight lang="lua">-- "Main" function to be called by wrapper or another module
function p._call_me(args)
    return "something" .. args["something"]
end
 
-- Wrapper function; to be called by template using {{#invoke}}
function p.call_me(frame)
    return p._call_me(frame.args)
end
 
-- Tester function; test wrapper that calls the "main" function
function p.tester()
    local args = { ["something"] = 123 }
    return p._call_me(args)
end</syntaxhighlight><syntaxhighlight lang="lua">-- Wrapper function; to be called by template
function p.call_me(frame)
    local arg = frame.args["arg"]
   
    -- Code goes here
   
    return call_me(arg)
end</syntaxhighlight>
 
==== Modules that serve as libraries ====
Modules that serve as libraries for other modules do not need a wrapper function, apart from the tester. Examples include [[Module:MOS]], [[Module:Rational]], and [[Module:Utils]].
 
Modules that serve as libraries for multiple, related templates may provide multiple wrapper functions. If a module provides multiple wrappers that each call a corresponding function, the name of the function called within the wrapper must be prefixed with an underscore.<syntaxhighlight lang="lua">-- MAIN FUNCTIONS
-- Usable by other modules
 
function p._call_me(arg1, arg2, arg3)
    -- Code goes here
end
 
function p._truncate(arg1)
    -- Code goes here
end
 
-- WRAPPER FUNCTIONS
-- Usable by templates with {{#invoke}}
 
function p._call_me(frame)
    return p._clamp(frame.args["arg1"], frame.args["arg2"], frame.args["arg3"])
end
 
function p.truncate(frame)
    return p._truncate(frame.args["arg1"])
end</syntaxhighlight>Modules that only provide one function may simply consist of that function as a return value. Example: [[Module:Yesno]].
 
==== Helper functions ====
For code readability and code reusability within the module, the use of helper functions is recommended.
 
Ideally, helper functions should be nested within the calling function if those helpers only serve that function, but this rule may be disregarded for testing purposes, or for helper functions needed by more than one function. Nested functions have access to the variables and parameters of the outer function, so an equivalent nested function may require fewer parameters.<syntaxhighlight lang="lua">function p._call_me(args)
    -- Get args here
    local arg1 = args["Arg 1"]
    local arg2 = args["Arg 2"]
   
    -- Helper function
    function helper_function(some_value)
        return "result" .. some_value
    end
end</syntaxhighlight>
 
==== What to pass into a "main" function ====
For an underscore-prefixed "main" function, if its expected inputs is determined to be fixed (for example, no new features are expected to ever be added), the function may accept them individually.<syntaxhighlight lang="lua">-- "Main" function to be called by wrapper or another module
-- Function signature consists of three args and the return value (not shown)
function p._call_me(arg1, arg2, arg3)
    -- Code goes here
end</syntaxhighlight>If there is large amounts of input, or if the number of inputs is not known, the function should have a single parameter that is a table of passed-in arguments. This allows for expansion of the template's inputs without making the function signature any larger.<syntaxhighlight lang="lua">
-- "Main" function to be called by wrapper or another module
-- Function signature consists of one table and the output (not shown)
function p._call_me(args)
    -- Get args here
    local arg1 = args["args1"]
    local arg2 = args["args2"]
    local arg3 = args["args3"]
   
    -- Code goes here
end
</syntaxhighlight>
 
==== What to get out of a function ====
Most functions should return something (a value, a string, a table, or more than one of those things), with the exception of functions that change the contents of a table. Modules that implement templates typically return a string that represents something that can be interpreted as wikitext. Guidance on how to create such strings is explained in later sections.
 
=== Concatenating strings ===
 
When concatenating long strings, it is best practice to insert constituent strings into a table, then concatenate afterwards. https://www.lua.org/pil/11.6.html
 
This rule does not apply to concatenating a few small strings together.
 
'''Preferred'''<syntaxhighlight lang="lua">
local lines = {}
table.insert(lines, '{| class="wikitable"')
table.insert(lines, '|+ Caption text')
table.insert(lines, '|-')
table.insert(lines, '! Header 1')
table.insert(lines, '! Header 2')
table.insert(lines, '! Header 3')
table.insert(lines, '|-')
table.insert(lines, '| aa')
table.insert(lines, '| bb')
table.insert(lines, '| cc')
table.insert(lines, '|-')
table.insert(lines, '| dd')
table.insert(lines, '| ee')
table.insert(lines, '| ff')
table.insert(lines, '|}')
 
return table.concat(lines, '\n')
</syntaxhighlight>'''Avoid'''<syntaxhighlight lang="lua">
local result = '{| class="wikitable"\n'
    .. '|+ Caption text\n'
    .. '|-\n'
    .. '! Header 1\n'
    .. '! Header 2\n'
    .. '! Header 3\n'
    .. '|-\n'
    .. '| aa\n'
    .. '| bb\n'
    .. '| cc\n'
    .. '|-\n'
    .. '| dd\n'
    .. '| ee\n'
    .. '| ff\n'
    .. '|}\n'
</syntaxhighlight>'''Allowed''' (although an alternative to this exists by using <code>string.format()</code>)<syntaxhighlight lang="lua">
local table_line = "Number of steps: " .. tonumber(num_steps) .. " steps"
</syntaxhighlight>
 
=== Mediawiki table formatting ===
Wikitables should be written with one line per cell instead of one line per row. This is for ease-of-reading when debugging the output of a module-generated table. Add a space between pipes/exclamation points and table entries to avoid accidentally adding new rows, such as when inputting negative numbers. Mediawiki tables generated using Lua code must follow this convention.
 
'''Preferred'''<syntaxhighlight lang="wikitext">{| class="wikitable"
|+ Caption text
|-
! Header 1
! Header 2
! Header 3
|-
| aa
| bb
| cc
|-
| dd
| ee
| ff
|}</syntaxhighlight>
 
'''Avoid'''
 
<syntaxhighlight lang="wikitext">{| class="wikitable"
|+ Caption text
|-
! Header 1 !! Header 2 !! Header 3
|-
| aa || bb || cc
|-
| dd || ee || ff
|}
</syntaxhighlight>
 
=== <code>ipairs</code> versus <code>pairs</code> versus <code>for</code> loop ===
 
<syntaxhighlight lang="lua">
local sometable = { "egg", "bread", "banana", nil, "milk" }
 
-- As a for loop
-- Order is guaranteed, but where to stop and start is needed
-- Iterates through all numeric indices, even if values are nil
for i = 1, #sometable do
    -- Code goes here
end
 
-- As a for loop using ipairs
-- Order is guaranteed, in ascending order
-- Iterates through numeric keys/indices, but stops at the first value of nil encountered
-- Obviates using sometable[i], as value has the same... value
for index, value in ipairs(sometable) do
    -- Code goes here
end


=== Function calls ===
-- As a for loop using pairs
Same as LuaRocks style guide.
-- Order is not guaranteed
-- Iterates through numeric and non-numeric keys
for key, value in pairs(sometable) do
    -- Code goes here
end
</syntaxhighlight>


==== Use of wrapper functions ====
Allowed.


=== Table attributes ===
== Templates and modules ==
''to be determined''


=== Blocks ===
=== Param names ===
''to be determined''
Capitalized, short, and descriptive parameter names are preferred wherever possible, such as <code>Scale Signature</code>, and not <code>scalesig</code> or <code>ssg</code>.


=== Spacing ===
Non-capitalized parameter names are used for debugging, testing, or meta-use (parameters used to build other templates and typically would never be seen in normal use), such as <code>name</code> and <code>debug</code>. Templates with simple usage can use non-capitalized parameter names throughout.
Use a space after <code>--</code>, used for comments. The lack of a space after <code>--</code> should indicate commented-out code.
Retrieved from "https://en.xen.wiki/w/User:Ganaram_inukshuk/Provisional_style_guide_for_Lua"