Go to file
Translation updater bot 81aa2d2590 Localisation updates from https://translatewiki.net.
Change-Id: Ic7b81058d159109a79f9907f527b585f57d6695e
2017-09-26 22:46:13 +02:00
doc
i18n Localisation updates from https://translatewiki.net. 2017-09-26 22:46:13 +02:00
images
includes build: Updating mediawiki/mediawiki-codesniffer to 13.0.0 2017-09-24 12:31:23 +00:00
resources Unify box-sizing to common LESS mixin 2017-09-21 15:32:09 -07:00
src Revert usage of Promise A+ in actions.js#fetch 2017-09-01 12:10:50 +02:00
tests Improve how we render help messages in preferences 2017-09-12 17:07:37 +00:00
.eslintrc.es5.json Run eslint on compiled assets to ensure code is es5 compatible 2017-09-07 12:30:33 +02:00
.eslintrc.json
.gitattributes
.gitignore
.gitreview
.istanbul.yml
.stylelintrc.json
CODE_OF_CONDUCT.md
composer.json build: Updating mediawiki/mediawiki-codesniffer to 13.0.0 2017-09-24 12:31:23 +00:00
COPYING
extension.json
Gemfile
Gemfile.lock
Gruntfile.js Run eslint on compiled assets to ensure code is es5 compatible 2017-09-07 12:30:33 +02:00
jsdoc.json
package.json
phpcs.xml
Popups.php
README.md
webpack.config.js

mediawiki/extensions/Popups

See https://www.mediawiki.org/wiki/Extension:Popups for more information about what it does.

Development

Popups uses an asset bundler so when developing for the extension you'll need to run a script to assemble the frontend assets.

You can find the frontend source files in src/, the compiled sources in resources/dist/, and other frontend assets managed by resource loader in resources/*.

After an npm install:

  • On one terminal, kickstart the bundler process:
    • npm start Will run the bundler in watch mode, re-assembling the files on file change.
    • npm run build Will compile the assets just once, ready for deployment. You must run this step before sending the patch or CI will fail (so that sources and built assets are in sync).
  • On another terminal, run tests and linting tools:
    • npm test To run the linting tools and the tests.
      • You can find the QUnit tests that depend on running MediaWiki under tests/qunit/
      • You can find the isolated QUnit tests under tests/node-qunit/, which you can run with npm run test:node
    • We recommend you install a file watcher like nodemon to watch sources and auto run linting and tests.
      • npm install -g nodemon
      • Example running linting and node unit tests:
        • nodemon -w src/ --exec "grunt lint:all && npm run test:node"
    • Get code coverage report with npm run coverage
      • Reports printed in the coverage/ folder