Page MenuHomePhabricator

Don't require extensions to set ConfigRegistry
Open, Needs TriagePublic


@Legoktm and I talked a bit about the configuration stuff and how it works with and in ExtensionRegistration. Legoktm's and my conclusion was, that it's a bit stupid to require extensions to set itself to ConfigRegistry, if they mostly( or even ever) add something like:

"ExtensionName": "GlobalVarConfig::newInstance"

(the only exception I know is CirrusSearch)

So, this should probably be changed in manifest_version 2, so that the ConfigRegistry is automatically created with a default (like GlobalVarConfig::newInstance), if the ConfigRegistry isn't set by the extension.

Event Timeline

Change 331953 had a related patch set uploaded (by Florianschmidtwelzow):
Automatically register a Config factory function for extensions

Removing task assignee due to inactivity, as this open task has been assigned to the same person for more than two years (see the emails sent to the task assignee on Oct27 and Nov23). Please assign this task to yourself again if you still realistically [plan to] work on this task - it would be welcome.
(See for tips how to best manage your individual work in Phabricator.)