Thijs/wiki.techinc.nl
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
wiki.techinc.nl/package.json

60 lines
1.8 KiB
JSON
Raw Normal View History

Set up node-jscs via Grunt (and pass it) * Set up Grunt via package.json (run `npm install` in mediawiki-core) * Add grunt task for node-jscs (NEW) This is a style checker (as opposed to jshint, which is for code quality). There are a few small style-related things that JSHint can check (camelcase, onevar etc.) but those are being deprecated in JSHint v3, people should use more sophisticated tools like node-jscs for this instead. As such this commit removes moves of those options from our jshint configuration. See: http://jshint.com/blog/jshint-3-plans/ * Add grunt task for jshint This will use the same jshint configuration as we use on Jenkins but makes it easier to run locally from the command line by being part of the same `$ grunt test` task list. Also: * Changed jshintignore to use "dir/**"" instead of "/dir" or "dir" because the latter is not compatible with Grunt for some reason. See also https://github.com/gruntjs/grunt-contrib-jshint/issues/126. Examples of coding style rules that were being violated that we can now catch in node-jscs: * Operator "," should stick to preceding expression * Missing space after "if" keyword * Multiple line break * Empty block (in jquery.textSelection and mediawiki.language) Bug: 54218 Change-Id: Ib9d7eab9f0d5cea5fb33f0b9f82e5554897fdfe0
2014-01-31 02:03:11 +00:00
{
build: Set package.json name If the project name isn't set, then `npm install` picks a value based on the directory name. If that isn't "core", then package-lock.json will overwrite the name property. Not a big deal, but may as well make this consistent for everyone. Change-Id: Idab76ffed4cd11fbc1659f090d51ffb3d43a96c5
2022-01-12 09:17:33 +00:00
"name": "core",
build: Updating npm dependencies * ini: 1.3.5 → 1.3.8 * https://npmjs.com/advisories/1589 Additional changes: * Removed useless -p option to phpcbf in "composer fix" command. * Set `root: true` in .eslintrc.json (T206485). Change-Id: I0116578751fd73e43b07c2830adc629f4b85c784
2021-01-03 22:29:28 +00:00
"private": true,
"scripts": {
build: Remove 'npm run api-testing-lint' command These files are already linted by 'npm test'. For running only the tests, there is no need to lint them first. If there are critical syntax errors than Node will report these in a useful way either way. For quick feedback on the right style during development, one can use an IDE plugin that provides it even quicker. Alternatively, one could use 'eslint path/to/subset' to run only the lint step. I've added a 'npm run lint' command to make this easier, e.g. when iterating on the style for contributors without an IDE plugin that want to confirm all lint failures from CI were addressed. Change-Id: Ic09de49543e50cb5ade241b45741fbdb397f9954
2021-05-21 20:26:26 +00:00
"api-testing": "mocha --timeout 0 --recursive tests/api-testing",
build: alphabetize package.json scripts no-op Change-Id: Ifc43411be7a7a37c7ac3a372bef1236eed71b0c4
2024-06-27 03:41:08 +00:00
"doc": "jsdoc -c jsdoc.json",
build: Remove 'npm run api-testing-lint' command These files are already linted by 'npm test'. For running only the tests, there is no need to lint them first. If there are critical syntax errors than Node will report these in a useful way either way. For quick feedback on the right style during development, one can use an IDE plugin that provides it even quicker. Alternatively, one could use 'eslint path/to/subset' to run only the lint step. I've added a 'npm run lint' command to make this easier, e.g. when iterating on the style for contributors without an IDE plugin that want to confirm all lint failures from CI were addressed. Change-Id: Ic09de49543e50cb5ade241b45741fbdb397f9954
2021-05-21 20:26:26 +00:00
"lint": "grunt lint",
build: alphabetize package.json scripts no-op Change-Id: Ifc43411be7a7a37c7ac3a372bef1236eed71b0c4
2024-06-27 03:41:08 +00:00
"minify:svg": "svgo --config=.svgo.config.js --quiet --recursive --folder resources/src --folder resources/assets",
"mocha": "mocha --timeout 0 --recursive",
build: Updating npm dependencies * ini: 1.3.5 → 1.3.8 * https://npmjs.com/advisories/1589 Additional changes: * Removed useless -p option to phpcbf in "composer fix" command. * Set `root: true` in .eslintrc.json (T206485). Change-Id: I0116578751fd73e43b07c2830adc629f4b85c784
2021-01-03 22:29:28 +00:00
"qunit": "grunt qunit",
selenium: Run most tests targeting the beta cluster Only creating account via the web interface does not work on the beta cluster, because of CAPTCHA. Bug: T323824 Change-Id: I7e9c6169f1c72450b4b620a8712629af7637f06b
2022-11-25 13:42:59 +00:00
"selenium-daily": "npm run selenium-test -- --mochaOpts.grep @daily",
build: alphabetize package.json scripts no-op Change-Id: Ifc43411be7a7a37c7ac3a372bef1236eed71b0c4
2024-06-27 03:41:08 +00:00
"selenium-test": "wdio ./tests/selenium/wdio.conf.js",
Add Jest to MW Core for testing Vue components This brings Jest to MW Core so that Vue components can more easily be tested. Packages ending with 'icons.json' are auto-mapped to the @wikimedia/codex-icons package, establishing a new convention. Jest is needed for testing Vue, but can be used for general JS testing as well. Documentation to come at https://www.mediawiki.org/wiki/Jest Usage: to run the tests, run "npx jest" or "npm run jest" in the root folder. This could be aliased to a "test:unit" script in package.json if desired. In order to make a Vue component testable, it is required to follow the `module.exports = exports` pattern. See: https://nodejs.org/api/modules.html#exports-shortcut A default jest.setup.js is added that mocks Core's mw global object, as well as providing the $i18n Vue plugin. This is based on Extension:GrowthExperiments (GPL-3.0-or-later). See https://w.wiki/B9vM An initial test for mediawiki.special.block is added, exemplifying how to mock calls to mw.config.get(). NOTE: The "overrides" added to package.json is a temporary measure to get around a current issue with caniuse-lite and the stylelint plugin that relies on it. See: https://github.com/RJWadley/stylelint-no-unsupported-browser-features/issues/299 Bug: T251790 Change-Id: I1af15e038d17b0f1c645fc5debf9db5846f6215c
2024-09-10 22:40:02 +00:00
"test": "grunt lint && npm run doc && npm run jest",
"jest": "jest --config tests/jest/jest.config.js"
build: Updating npm dependencies * ini: 1.3.5 → 1.3.8 * https://npmjs.com/advisories/1589 Additional changes: * Removed useless -p option to phpcbf in "composer fix" command. * Set `root: true` in .eslintrc.json (T206485). Change-Id: I0116578751fd73e43b07c2830adc629f4b85c784
2021-01-03 22:29:28 +00:00
},
"devDependencies": {
build: Update 'svgo' to latest v3.2.0 The latest update of 'svgo' dependency includes three optimizations on converting path commands, which - improves closing paths and how we determine if to use absolute or relative commands. - round arc or convert to lines based on the geometric sagitta - convert cubic Bézier curves to quadratic Bézier curves where possible Also unifiying npm command to qua standard notation `minify:svg`. Bug: T354875 Change-Id: Iaa9857ad95a1247fa0751f3953d324ea5c83b92c
2024-01-12 17:42:49 +00:00
"@apidevtools/swagger-parser": "^10.1.0",
Add Jest to MW Core for testing Vue components This brings Jest to MW Core so that Vue components can more easily be tested. Packages ending with 'icons.json' are auto-mapped to the @wikimedia/codex-icons package, establishing a new convention. Jest is needed for testing Vue, but can be used for general JS testing as well. Documentation to come at https://www.mediawiki.org/wiki/Jest Usage: to run the tests, run "npx jest" or "npm run jest" in the root folder. This could be aliased to a "test:unit" script in package.json if desired. In order to make a Vue component testable, it is required to follow the `module.exports = exports` pattern. See: https://nodejs.org/api/modules.html#exports-shortcut A default jest.setup.js is added that mocks Core's mw global object, as well as providing the $i18n Vue plugin. This is based on Extension:GrowthExperiments (GPL-3.0-or-later). See https://w.wiki/B9vM An initial test for mediawiki.special.block is added, exemplifying how to mock calls to mw.config.get(). NOTE: The "overrides" added to package.json is a temporary measure to get around a current issue with caniuse-lite and the stylelint plugin that relies on it. See: https://github.com/RJWadley/stylelint-no-unsupported-browser-features/issues/299 Bug: T251790 Change-Id: I1af15e038d17b0f1c645fc5debf9db5846f6215c
2024-09-10 22:40:02 +00:00
"@babel/preset-env": "7.25.4",
package.json: add pinia and @pinia/testing The upcoming Multiblocks project will make use of a Pinia store, which is already shipped in MediaWiki via ResourceLoader. In order to continue to test Vue components that make use of a store, we need the Pinia testing utilities. The 'pinia' package is locked to the same version that's in RL, 2.0.16, while '@pinia/testing' is locked at 0.0.12, the same version used by some extensions such as GrowthExperiments. Bug: T251790 Change-Id: Ia88d987bf7e5afa1a17d63b4ebc96448ccec2f6c
2024-10-15 21:39:43 +00:00
"@pinia/testing": "0.0.12",
Add Jest to MW Core for testing Vue components This brings Jest to MW Core so that Vue components can more easily be tested. Packages ending with 'icons.json' are auto-mapped to the @wikimedia/codex-icons package, establishing a new convention. Jest is needed for testing Vue, but can be used for general JS testing as well. Documentation to come at https://www.mediawiki.org/wiki/Jest Usage: to run the tests, run "npx jest" or "npm run jest" in the root folder. This could be aliased to a "test:unit" script in package.json if desired. In order to make a Vue component testable, it is required to follow the `module.exports = exports` pattern. See: https://nodejs.org/api/modules.html#exports-shortcut A default jest.setup.js is added that mocks Core's mw global object, as well as providing the $i18n Vue plugin. This is based on Extension:GrowthExperiments (GPL-3.0-or-later). See https://w.wiki/B9vM An initial test for mediawiki.special.block is added, exemplifying how to mock calls to mw.config.get(). NOTE: The "overrides" added to package.json is a temporary measure to get around a current issue with caniuse-lite and the stylelint plugin that relies on it. See: https://github.com/RJWadley/stylelint-no-unsupported-browser-features/issues/299 Bug: T251790 Change-Id: I1af15e038d17b0f1c645fc5debf9db5846f6215c
2024-09-10 22:40:02 +00:00
"@vue/test-utils": "2.4.6",
"@vue/vue3-jest": "29.2.6",
selenium: Update @wdio to the latest v7 versions Required for running tests using Firefox. Bug: T351747 Change-Id: I19d247d559eff06fc0aebac79f0d31b6ef65170a
2023-11-22 15:18:58 +00:00
"@wdio/cli": "7.33.0",
"@wdio/junit-reporter": "7.33.0",
"@wdio/local-runner": "7.33.0",
"@wdio/mocha-framework": "7.33.0",
"@wdio/spec-reporter": "7.33.0",
Update Codex from v1.13.1 to v1.14.0 Bug: T362650 Bug: T370057 Bug: T371118 Bug: T374659 Bug: T374882 Bug: T375699 Bug: T375700 Bug: T376024 Bug: T376622 Change-Id: I18684997862a1a6427627d8061a2583fff00e621
2024-10-16 15:39:59 +00:00
"@wikimedia/codex": "1.14.0",
"@wikimedia/codex-icons": "1.14.0",
build: Update karma-firefox-launcher to fix bug on macOS Mozilla has stopped shipping the `Firefox.app/Contents/MacOS/firefox-bin` entrypoint for macOS, instead favouring `Firefox.app/Contents/MacOS/firefox`. This broke the launcher and requires a minor patch. Pending an upstream release, use our fork for now. We can transition this to a simpler setup without Karma (i.e. launch browser directly), but for now we can patch it in this way. Change-Id: If99f030b1b23be6b906a15bfdb72590fc249cb0c
2024-02-09 13:46:06 +00:00
"@wikimedia/karma-firefox-launcher": "2.1.3",
build: Upgrade api-testing from 1.5.1 to 1.6.0 Bug: T333134 Change-Id: I8a9a3c3b2ba641806a6c75ffb852238b1a1d7606
2023-04-12 18:39:10 +00:00
"api-testing": "1.6.0",
Rest: Move TransformHandler to core (part 1) Begin moving the transform endpoints and handler class to MediaWiki core. Bug: T301370 Change-Id: I94e9d2e8d497c1992c542001afe333fa7537e553
2022-05-26 12:57:29 +00:00
"domino": "2.1.0",
build: Updating npm dependencies * ini: 1.3.5 → 1.3.8 * https://npmjs.com/advisories/1589 Additional changes: * Removed useless -p option to phpcbf in "composer fix" command. * Set `root: true` in .eslintrc.json (T206485). Change-Id: I0116578751fd73e43b07c2830adc629f4b85c784
2021-01-03 22:29:28 +00:00
"dotenv": "8.2.0",
build: Update eslint-config-wikimedia to 0.28.2 Fixes false positive with no-jquery/no-extend Change-Id: I4f7e8da89da3a7433e0fcd82b7bb341ad4d0068c
2024-06-13 13:47:43 +00:00
"eslint-config-wikimedia": "0.28.2",
build: Upgrade grunt from 1.5.3 to 1.6.1 Change-Id: I8a71615e6cf70e07f60b97f5d53ed2da1faa8642
2023-02-07 15:19:44 +00:00
"grunt": "1.6.1",
build: Updating grunt-banana-checker to 0.13.0 Change-Id: Ie15fafb908815c34784effbdcbc0613a21262094
2024-05-18 00:20:45 +00:00
"grunt-banana-checker": "0.13.0",
build: Updating npm dependencies * ini: 1.3.5 → 1.3.8 * https://npmjs.com/advisories/1589 Additional changes: * Removed useless -p option to phpcbf in "composer fix" command. * Set `root: true` in .eslintrc.json (T206485). Change-Id: I0116578751fd73e43b07c2830adc629f4b85c784
2021-01-03 22:29:28 +00:00
"grunt-contrib-watch": "1.1.0",
build: Update linters Change-Id: I35fa6b68e1ffdc563bd49de06d8ba11561f9cfdc
2023-08-21 15:33:43 +00:00
"grunt-eslint": "24.3.0",
build: Update stylelint-config-wikimedia to 0.12.0 Change-Id: Ifb215e45a2ad4574fa821c696199e8c5911ba3ae
2022-02-19 13:52:17 +00:00
"grunt-karma": "4.0.2",
build: Update stylelint-config-wikimedia to 0.17.2 Change-Id: I8d68bcae416463ceec6d7b617e38d34c57360698
2024-06-05 18:05:23 +00:00
"grunt-stylelint": "0.20.0",
Add Jest to MW Core for testing Vue components This brings Jest to MW Core so that Vue components can more easily be tested. Packages ending with 'icons.json' are auto-mapped to the @wikimedia/codex-icons package, establishing a new convention. Jest is needed for testing Vue, but can be used for general JS testing as well. Documentation to come at https://www.mediawiki.org/wiki/Jest Usage: to run the tests, run "npx jest" or "npm run jest" in the root folder. This could be aliased to a "test:unit" script in package.json if desired. In order to make a Vue component testable, it is required to follow the `module.exports = exports` pattern. See: https://nodejs.org/api/modules.html#exports-shortcut A default jest.setup.js is added that mocks Core's mw global object, as well as providing the $i18n Vue plugin. This is based on Extension:GrowthExperiments (GPL-3.0-or-later). See https://w.wiki/B9vM An initial test for mediawiki.special.block is added, exemplifying how to mock calls to mw.config.get(). NOTE: The "overrides" added to package.json is a temporary measure to get around a current issue with caniuse-lite and the stylelint plugin that relies on it. See: https://github.com/RJWadley/stylelint-no-unsupported-browser-features/issues/299 Bug: T251790 Change-Id: I1af15e038d17b0f1c645fc5debf9db5846f6215c
2024-09-10 22:40:02 +00:00
"jest": "29.7.0",
"jest-environment-jsdom": "29.7.0",
Update jsdoc-wmf-theme from 0.0.12 to 0.0.13 Update jsdoc 3.6.10 to 4.0.2 Change-Id: I88f4ae48ca7b60d370daa729daf2c6f68ce0648f
2024-03-05 16:11:23 +00:00
"jsdoc": "4.0.2",
Update jsdoc-wmf-theme from 1.0.1 to 1.1.0 * Use the new default set of plugins * Remove prefixMap since that is now handled by the theme * Remove linkMap items provided by the theme * Replace the JSDoc-specific package.json with a maintitle and README h1 * Add node_modules/jsdoc-class-hierarchy as a dependency. This plugin isn't currently used in core, but it is part of the default plugin set. Bug: T368081 Change-Id: Ib2b16b2f4c5f11ff29cc6dc5d67df43bc59c9752
2024-06-25 15:53:10 +00:00
"jsdoc-wmf-theme": "1.1.0",
build: Updating dependencies composer: * mediawiki/mediawiki-codesniffer: 38.0.0 → 39.0.0 The following sniffs are failing and were disabled: * MediaWiki.PHPUnit.AssertEmpty.AssertEmptyUsed * php-parallel-lint/php-console-highlighter: 0.5 → 1.0.0 * php-parallel-lint/php-parallel-lint: 1.3.1 → 1.3.2 npm: * grunt-banana-checker: 0.9.0 → 0.10.0 * grunt: 1.5.2 → 1.5.3 * karma: 6.3.15 → 6.4.1 * async: 2.6.3 → 2.6.4 * https://github.com/advisories/GHSA-fwr7-v2mv-hh25 * got: 11.8.3 → 11.8.5 * https://github.com/advisories/GHSA-pfrx-2q88-qq97 Change-Id: I1d7bc9c9599b48d2bd837617cad409a31adb362a
2022-10-07 17:35:34 +00:00
"karma": "6.4.1",
build: Updating npm dependencies * ini: 1.3.5 → 1.3.8 * https://npmjs.com/advisories/1589 Additional changes: * Removed useless -p option to phpcbf in "composer fix" command. * Set `root: true` in .eslintrc.json (T206485). Change-Id: I0116578751fd73e43b07c2830adc629f4b85c784
2021-01-03 22:29:28 +00:00
"karma-chrome-launcher": "3.1.0",
"karma-mocha-reporter": "2.2.5",
build: Update karma-qunit to 4.2.0 and remove old `__karma__` hack Made redundant by https://github.com/karma-runner/karma-qunit/pull/184. Change-Id: If636ec52826c2bdcf1b6809e8ff18e34179cd71d
2024-02-10 16:48:03 +00:00
"karma-qunit": "4.2.0",
package.json: add pinia and @pinia/testing The upcoming Multiblocks project will make use of a Pinia store, which is already shipped in MediaWiki via ResourceLoader. In order to continue to test Vue components that make use of a store, we need the Pinia testing utilities. The 'pinia' package is locked to the same version that's in RL, 2.0.16, while '@pinia/testing' is locked at 0.0.12, the same version used by some extensions such as GrowthExperiments. Bug: T251790 Change-Id: Ia88d987bf7e5afa1a17d63b4ebc96448ccec2f6c
2024-10-15 21:39:43 +00:00
"pinia": "2.0.16",
tests: Upgrade QUnit from v2.19.4 to v2.20.0 Change-Id: I9a870d937efee1588fb87584f65a985cb0d03693
2023-10-20 18:58:55 +00:00
"qunit": "2.20.0",
build: Update stylelint-config-wikimedia to 0.17.2 Change-Id: I8d68bcae416463ceec6d7b617e38d34c57360698
2024-06-05 18:05:23 +00:00
"stylelint-config-wikimedia": "0.17.2",
build: Update 'svgo' to latest v3.2.0 The latest update of 'svgo' dependency includes three optimizations on converting path commands, which - improves closing paths and how we determine if to use absolute or relative commands. - round arc or convert to lines based on the geometric sagitta - convert cubic Bézier curves to quadratic Bézier curves where possible Also unifiying npm command to qua standard notation `minify:svg`. Bug: T354875 Change-Id: Iaa9857ad95a1247fa0751f3953d324ea5c83b92c
2024-01-12 17:42:49 +00:00
"svgo": "3.2.0",
Add Jest to MW Core for testing Vue components This brings Jest to MW Core so that Vue components can more easily be tested. Packages ending with 'icons.json' are auto-mapped to the @wikimedia/codex-icons package, establishing a new convention. Jest is needed for testing Vue, but can be used for general JS testing as well. Documentation to come at https://www.mediawiki.org/wiki/Jest Usage: to run the tests, run "npx jest" or "npm run jest" in the root folder. This could be aliased to a "test:unit" script in package.json if desired. In order to make a Vue component testable, it is required to follow the `module.exports = exports` pattern. See: https://nodejs.org/api/modules.html#exports-shortcut A default jest.setup.js is added that mocks Core's mw global object, as well as providing the $i18n Vue plugin. This is based on Extension:GrowthExperiments (GPL-3.0-or-later). See https://w.wiki/B9vM An initial test for mediawiki.special.block is added, exemplifying how to mock calls to mw.config.get(). NOTE: The "overrides" added to package.json is a temporary measure to get around a current issue with caniuse-lite and the stylelint plugin that relies on it. See: https://github.com/RJWadley/stylelint-no-unsupported-browser-features/issues/299 Bug: T251790 Change-Id: I1af15e038d17b0f1c645fc5debf9db5846f6215c
2024-09-10 22:40:02 +00:00
"vue": "3.4.27",
api-testing: make xmls2js a devDependency xml2js was accidentally aded as a regular dependency in Idb5b0d21a. Change-Id: I22bdcf61b0e6dd0623cf973df89b991d2504e3c4
2024-05-21 20:10:30 +00:00
"wdio-mediawiki": "file:tests/selenium/wdio-mediawiki",
REST: introduce OpenSearchDescriptionHandler Move open search description endpoint from /w/opensource_desc.php to /w/rest.php/v1/search. Bug: T363984 Change-Id: Idb5b0d21adc6152ef77e6d17846b6acc6a904e01
2024-05-02 10:57:40 +00:00
"xml2js": "^0.6.2"
Add Jest to MW Core for testing Vue components This brings Jest to MW Core so that Vue components can more easily be tested. Packages ending with 'icons.json' are auto-mapped to the @wikimedia/codex-icons package, establishing a new convention. Jest is needed for testing Vue, but can be used for general JS testing as well. Documentation to come at https://www.mediawiki.org/wiki/Jest Usage: to run the tests, run "npx jest" or "npm run jest" in the root folder. This could be aliased to a "test:unit" script in package.json if desired. In order to make a Vue component testable, it is required to follow the `module.exports = exports` pattern. See: https://nodejs.org/api/modules.html#exports-shortcut A default jest.setup.js is added that mocks Core's mw global object, as well as providing the $i18n Vue plugin. This is based on Extension:GrowthExperiments (GPL-3.0-or-later). See https://w.wiki/B9vM An initial test for mediawiki.special.block is added, exemplifying how to mock calls to mw.config.get(). NOTE: The "overrides" added to package.json is a temporary measure to get around a current issue with caniuse-lite and the stylelint plugin that relies on it. See: https://github.com/RJWadley/stylelint-no-unsupported-browser-features/issues/299 Bug: T251790 Change-Id: I1af15e038d17b0f1c645fc5debf9db5846f6215c
2024-09-10 22:40:02 +00:00
},
"overrides": {
"caniuse-lite": "1.0.30001653"
api-testing: Update to 1.5.0 Depends-On: Ifb6fc6f3036c1623c32418c5f304b6fc7196fa04 Bug: T298735 Change-Id: I31966e96a996d30fb31f401abecff47a893b8f0c
2022-01-11 08:48:46 +00:00
}
Set up node-jscs via Grunt (and pass it) * Set up Grunt via package.json (run `npm install` in mediawiki-core) * Add grunt task for node-jscs (NEW) This is a style checker (as opposed to jshint, which is for code quality). There are a few small style-related things that JSHint can check (camelcase, onevar etc.) but those are being deprecated in JSHint v3, people should use more sophisticated tools like node-jscs for this instead. As such this commit removes moves of those options from our jshint configuration. See: http://jshint.com/blog/jshint-3-plans/ * Add grunt task for jshint This will use the same jshint configuration as we use on Jenkins but makes it easier to run locally from the command line by being part of the same `$ grunt test` task list. Also: * Changed jshintignore to use "dir/**"" instead of "/dir" or "dir" because the latter is not compatible with Grunt for some reason. See also https://github.com/gruntjs/grunt-contrib-jshint/issues/126. Examples of coding style rules that were being violated that we can now catch in node-jscs: * Operator "," should stick to preceding expression * Missing space after "if" keyword * Multiple line break * Empty block (in jquery.textSelection and mediawiki.language) Bug: 54218 Change-Id: Ib9d7eab9f0d5cea5fb33f0b9f82e5554897fdfe0
2014-01-31 02:03:11 +00:00
}
Reference in a new issue Copy permalink