Modul:Protection banner: Unterschied zwischen den Versionen

-- Get the expiry key fragment.

local expiryFragment

if self.expiry == 'indef' then

expiryFragment = self.expiry

elseif type(self.expiry) == 'number' then

expiryFragment = 'temp'

-- Get the namespace key fragment.

local namespaceFragment

namespaceFragment = cfg.categoryNamespaceKeys[title.namespace]

if not namespaceFragment and title.namespace % 2 == 1 then

namespaceFragment = 'talk'

-- Define the order that key fragments are tested in. This is done with an

-- array of tables containing the value to be tested, along with its

-- position in the cfg.protectionCategories table.

local order = {

{val = expiryFragment,   keypos = 1},

{val = namespaceFragment, keypos = 2},

{val = self.reason,       keypos = 3},

{val = self.level,       keypos = 4},

{val = self.action,       keypos = 5}

 

-- To generate the correct category for some reason values, we need to

-- prioritise the position of the namespace key fragment over that of the

-- reason key fragment. For these reasn values, swap the namespace subtable

-- and the reason subtable around.

if self.reason and cfg.reasonsWithNamespacePriority[self.reason] then

table.insert(order, 3, table.remove(order, 2))

-- Define the attempt order. Inactive subtables (subtables with nil "value"

-- fields) are moved to the end, where they will later be given the key

-- "all". This is to cut down on the number of table lookups in

-- cfg.protectionCategories, which grows exponentially with the number of

-- non-nil keys. We keep track of the number of active subtables with the

-- noActive parameter.

for i, t in ipairs(order) do

-- Check increasingly generic key combinations until we find a match. If a

-- specific category exists for the combination of key fragments we are

-- given, that match will be found first. If not, we keep trying different

-- key fragment combinations until we match using the key

-- To generate the keys, we index the key subtables using a binary matrix

-- with indexes i and j. j is only calculated up to the number of active

-- subtables. For example, if there were three active subtables, the matrix

-- would look like this, with 0 corresponding to the key fragment "all", and

-- 1 corresponding to other key fragments.

-- Values of j higher than the number of active subtables are set

-- A key for cfg.protectionCategories is constructed for each value of i.

-- The position of the value in the key is determined by the keypos field in

-- each subtable.

key[t.keypos] = 'all'

key[t.keypos] = t.val

key[t.keypos] = 'all'