mirror of
https://gerrit.wikimedia.org/r/mediawiki/extensions/Popups
synced 2024-09-25 03:09:14 +00:00
293d7ebe8d
Given that interactions end up with an event logged, there shouldn't be a reason to keep an interaction active after it's corresponding final event has been logged. See Tbayer's state graph. This patch removes the current interaction if an event with that token is logged, effectively finalizing it and making it impossible for the token to be reused from the state tree again. Additional changes: * Pass the logged event with the action EVENT_LOGGED so that the reducer can determine if it needs to do anything else. * Since the interaction is removed, when undefined, guard against actions that use state.interaction freely. (Only allow BOOT, LINK_PREVIEW, and EVENT_LOGGED) Bug: T161769 Bug: T163198 Change-Id: I99fd5716dc17da32929b6e8ae4aa164f9d84c387 |
||
---|---|---|
doc | ||
i18n | ||
images | ||
includes | ||
resources | ||
src | ||
tests | ||
.eslintrc.json | ||
.gitattributes | ||
.gitignore | ||
.gitreview | ||
.istanbul.yml | ||
.stylelintrc | ||
composer.json | ||
COPYING | ||
extension.json | ||
Gemfile | ||
Gemfile.lock | ||
Gruntfile.js | ||
jsduck.json | ||
package.json | ||
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 withnpm run test:node
- You can find the QUnit tests that depend on running MediaWiki under
- 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
- Reports printed in the