Difference between revisions of "Module:Changes"
Jump to navigation
Jump to search
m (No point making s to not use it) |
m (Cue masses of testing) |
||
| Line 10: | Line 10: | ||
args = f:getParent().args | args = f:getParent().args | ||
end | end | ||
return "change" .. n | |||
end | |||
--[[ | |||
repeat s = args["change" .. n] | repeat s = args["change" .. n] | ||
groups[n] = "<li>" .. s .. "</li>" | groups[n] = "<li>" .. s .. "</li>" | ||
| Line 27: | Line 29: | ||
return back | return back | ||
end | end | ||
--]] | |||
return p | return p | ||
Revision as of 17:15, 10 February 2015
Replacement Lua scripting to do what Template:Changes does/did, but in a more flexible way.
- It supports the new structure of Version History.
- It can have as many changes as needed, providing that they go up sequencially, and numbers are not missed out (change1, change2, change3 is ok, but change1, change3 isn't).
- It should be faster.
Message me (Chocohead) either on the wiki (here) or on the Forum if you find any problems.
The above documentation is transcluded from Module:Changes/doc. (edit | history)
local p = {}
-- Changes
function p.changes( f )
local groups = {}
local s = nil
local n = 1
if f == mw.getCurrentFrame() then
args = f:getParent().args
end
return "change" .. n
end
--[[
repeat s = args["change" .. n]
groups[n] = "<li>" .. s .. "</li>"
n = n + 1
until s == nil
--for i = 1,loop,1 do
--s = args["change" .. i]
--groups[i] = "<li>" .. s .. "</li>"
--end
local back = "Arguments <br/>"
for key,value in pairs(groups) do
back = back .. value .. "<br/>"
end
return back
end
--]]
return p