wikimedia/mediawiki-extensions-Popups
1
0
Fork 0
mirror of https://gerrit.wikimedia.org/r/mediawiki/extensions/Popups synced 2024-11-27 17:00:37 +00:00
Code Issues Packages Projects Releases Wiki Activity
Mirror of https://gerrit.wikimedia.org/g/mediawiki/extensions/Popups
1345 commits 12 branches 16 tags 68 MiB
JavaScript 84.7%
PHP 9.9%
Less 5%
Shell 0.4%
Go to file
Bartosz Dziewoński 2b637e42ef Improve how we render help messages in preferences 
* The 'help' parameter expects a string, not a Message object. It
  seemed to be working, but caused fatals when switching the
  preferences form to the OOUI implementation (T117781).
* Use 'help-message' instead, which also avoids using the global
  request context for Message objects.

Bug: T117781
Change-Id: I5b2e44df35a2696da0e7ba8394eccf41914f6dda
2017-09-12 17:07:37 +00:00
doc Docs: Fix typo in Grafana link label 2017-08-26 00:08:03 +01:00
i18n Localisation updates from https://translatewiki.net. 2017-09-09 00:12:05 +02:00
images Optimise SVGs with svgo 2017-04-26 17:15:45 +01:00
includes Improve how we render help messages in preferences 2017-09-12 17:07:37 +00:00
resources Revert usage of Promise A+ in actions.js#fetch 2017-09-01 12:10:50 +02: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 Explicitly set ecmaVersion for eslint 2017-08-30 13:47:49 +02:00
.gitattributes Hygiene: Move build/ext.popups/ to src/ 2017-02-14 09:59:59 -08:00
.gitignore Generate docs inside doc folder 2017-05-30 10:16:57 -04:00
.gitreview Merge remote-tracking branch 'gerrit/mpga' 2017-02-14 11:20:17 -08:00
.istanbul.yml Hygiene: Tidy up QUnit references 2017-05-04 15:53:44 +01:00
.stylelintrc.json Use json extension for .stylelintrc 2017-08-19 10:19:38 +02:00
CODE_OF_CONDUCT.md Add CODE_OF_CONDUCT.md 2017-06-07 15:30:07 +04:30
composer.json build: Updating mediawiki/mediawiki-codesniffer to 0.12.0 2017-09-01 04:55:51 +00:00
COPYING Add COPYING file 2014-02-06 15:38:46 +05:30
extension.json Use canonical name for NS_SPECIAL titles when checking the blacklist 2017-08-25 15:56:02 +02:00
Gemfile doc: Replace JSDuck v5.3.4 with JSDoc v3.4.3 2017-05-23 05:33:31 +01:00
Gemfile.lock Hygiene: Remove RL-related step 2016-12-13 14:46:03 +00:00
Gruntfile.js Run eslint on compiled assets to ensure code is es5 compatible 2017-09-07 12:30:33 +02:00
jsdoc.json Generate docs inside doc folder 2017-05-30 10:16:57 -04:00
package.json Merge "Use EcmaScript modules instead of common.js modules" 2017-08-07 22:13:51 +00:00
phpcs.xml build: Updating mediawiki/mediawiki-codesniffer to 0.12.0 2017-09-01 04:55:51 +00:00
Popups.php Hygiene: Update required MediaWiki version 2017-07-24 16:12:03 +02:00
README.md Add code coverage reports npm script 2017-03-03 13:34:33 +01:00
webpack.config.js Store map files under .json extension 2017-08-29 21:18:35 +02:00

README.md

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