Page MenuHomePhabricator

Create scaffolding for on-wiki page performance inspector
Closed, ResolvedPublic


The first step for getting T117411 going is to create a well-structured
extension skeleton that can serve as a good foundation for the development

This means:

  • an extension.json file
  • an i18n/ subdirectory with qqq.json / en.json
  • .jscsrc / jsduck.json / .jshintrc
  • a tests/ directory with at least:
    • one dummy PHPUnit test
    • one dummy QUnit test
  • an appropriate license
  • a stub page on
  • configure CI -
  • CI entry points
    • npm test (banana i18n checker, jshint, jsonlint...)
    • composer test (phplint)
  • two ResourceLoader modules:
    • one which draws an interface element that activates the interface by mw.loader.using()-ing the second module
    • the main module itself.

For guidance, Manual:Developing extensions is a good place to start. If you need an example, have a look at the MassMessage extension.

A reference repo is BoilerPlate extension.

CI entry points are listed at

Event Timeline

ori assigned this task to Peter.
ori raised the priority of this task from to Needs Triage.
ori updated the task description. (Show Details)
ori added a project: Performance-Team.
ori added subscribers: Gilles, aaron, Krinkle and 3 others.
ori triaged this task as Medium priority.Nov 9 2015, 7:37 PM
ori set Security to None.

Change 256199 had a related patch set uploaded (by Phedenskog):
Test the PerformanceInspector extension

mediawiki/extensions/BoilerPlate usually fills all your needs :-}

Change 256199 merged by jenkins-bot:
Test the PerformanceInspector extension

Change 257551 had a related patch set uploaded (by Phedenskog):
Scaffolding for the Performance Inspector

Change 257551 merged by jenkins-bot:
Scaffolding for the Performance Inspector

Change 271589 had a related patch set uploaded (by Phedenskog):
Setup resource loader modules and structure

Change 271589 merged by jenkins-bot:
Initial POC of inspector dialogs and module structure