4 commits

Author	SHA1	Message	Date
Reedy	48a60aa762	Various minor code cleanup ... Change-Id: I75f34c66f1c1968cfb9a3e1932068ec2420e0fa6	2024-10-30 01:48:33 +00:00
Reedy	30cd1d8a23	Namespace base classes ... Change-Id: I3fa9747e0ea970c5de39e2da8603e1bba9388a69	2022-07-30 18:13:03 +00:00
Reedy	274e6079f8	Fix PSR12.Properties.ConstantVisibility.NotFound ... Change-Id: Ib76375fed58fddb1f96728dd2baeec08e222dc83	2020-04-15 00:25:50 +01:00
Florian Schmidt	50bc57a200	Allow other extensions to setup triggers using attributes ... Instead of misusing the config section of extension.json to declare captcha triggers in the ConfirmEdits CaptchaTriggers config variable, other extensions can now use the CaptchaTriggers attribute for the exact same thing. E.g., to declare a new trigger, the following addition to the own extension.json will register the trigger in ConfirmEdit: "CaptchaTriggers": { "wikiforum": true } This also removes the CaptchaClass config from the main extension.json config section, and automatically sets the SimpleCaptcha module in the getInstance() method of ConfirmEditHooks, which is a pre-requirement for the mediawiki/core change Ieeb26011e42c741041d2c3252238ca0823b99eb4. Bug: T152929 Change-Id: I4c5eaf87657f5dc07787480a2f1a56a1db8c714f	2017-09-02 17:45:26 +02:00