Echo, Flow, and a few other extensions use core's includes/utils/AutoloadGenerator.php to generate an autoload.php file that appends to $wgAutoloadClasses. As we convert to extension registration, this should be adapted to, e.g. load extension.json file, add the class map to its "AutoloadClasses" key, and write out the new extension.json.
Description
Description
Event Timeline
Comment Actions
Hi! I am new here and want to work on this task. A doubt: Is the script supposed to do something other than what it is currently doing, if extension.json does not exist?
Comment Actions
Hi! Sorry I missed you on IRC. So I was imagining that AutoloadGenerator::generateAutoload() would check to see if a extension.json exists, and update it if that was the case. Otherwise it'll just update autoload.php if that file exists..
Comment Actions
Change 213468 had a related patch set uploaded (by Galorefitz):
AutoloadGenerator.php: Update 'AutoloadClasses' in extension.json
Comment Actions
Change 213468 merged by jenkins-bot:
AutoloadGenerator.php: Update 'AutoloadClasses' in extension.json
Comment Actions
Change 217590 had a related patch set uploaded (by Paladox):
AutoloadGenerator.php: Update 'AutoloadClasses' in extension.json
Comment Actions
Change 217768 had a related patch set uploaded (by Mattflaschen):
Also support skin.json for updating JSON AutoloadClasses
Comment Actions
Change 217590 abandoned by Legoktm:
AutoloadGenerator.php: Update 'AutoloadClasses' in extension.json
Reason:
Doesn't need to be backported
Comment Actions
Change 217768 merged by jenkins-bot:
Also support skin.json for updating JSON AutoloadClasses