Allow adding metadata to config options in extension.json
Closed, ResolvedPublic
Actions

Description

Right now the "config" section is a simple mapping of name → value. We also have "magic" keys like _prefix and _merge_strategy. I'd like us to be able to add more metadata to individual config options in the future, so something like:

{
	"config": {
		"FooBar": {
			"public": true,
			"value": "baz",
			"merge_strategy": "array_plus"
		}
	}
}

Mostly this would give us significantly more flexibility in the future instead of using hacky underscore prefixed keys. This would be part of manifest_version 2, and I'd like to get it into 1.27.

Details

Related Gerrit Patches:

mediawiki/core : master

registration: Convert "config" into an object with metadata

Related Objects
Search...

Status	Assigned	Task
Open	None	T119117 Get rid of $wg = $wmg hack for extensions that have been converted to using extension.json
Open	None	T140850 Remove all PHP entry points from all Wikimedia-deployed extensions and skins
Open	None	T140851 Un-comment the wfWarn deprecations in all PHP entry points from all Wikimedia-deployed extensions and skins
Open	None	T125678 Scap should not rely on extension-list, instead pass --extension-dir to mergeMessageFileList.php
Open	None	T140852 Load all Wikimedia-deployed extensions and skins via extension registration
Open	None	T87875 Convert all Wikimedia-deployed extensions and skins to use extension registration
Resolved	lcawte	T87984 Convert TorBlock to use extension registration
Resolved	Parent5446	T87883 Convert Babel to use extension registration
Resolved	MtDu	T88065 [TrustedXFF] Convert TrustedXFF to use extension registration
Resolved	Legoktm	T100956 Support configuration settings that are filesystem paths in extension.json
Resolved	Legoktm	T133626 Allow adding metadata to config options in extension.json

Event Timeline

Legoktm created this task.Apr 26 2016, 1:02 AM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 26 2016, 1:02 AM

I'm pretty sure you've something in mind with the "public" key, but I'm not sure what? :)

Generally speaken: I would welcome this, as it definitely gives us a lot more flexibility in this part of extension registration.

"public" was just an example of something I want to add in the future for when we start displaying config settings and their values on-wiki as part of config db, it wouldn't be part of this bug.

Florian moved this task from Backlog to Extension registration manifest_version 2 on the MediaWiki-Configuration board.Apr 29 2016, 9:03 PM

This would let us fix T100956: Support configuration settings that are filesystem paths in extension.json neatly for example.

@Legoktm: I'm not entirely sure what "would be part of manifest_version 2" mean from an implemantation point of view. My idea would be to still support string values only