| commit | d285e62f5c7a895d1441c43b805a3abe2f010ee3 | [log] [tgz] |
|---|---|---|
| author | Translation updater bot <l10n-bot@translatewiki.net> | Wed Jan 01 08:22:52 2025 +0100 |
| committer | Translation updater bot <l10n-bot@translatewiki.net> | Wed Jan 01 08:22:52 2025 +0100 |
| tree | 2bfd2ba4740c45fc97f65ad75e12971cc33d6c5e | |
| parent | f224de658b08377bf9cc93454826bd7ee3fcb969 [diff] |
Localisation updates from https://translatewiki.net. Change-Id: I56715fdc0ef20b42e54193d9faec19cc8c1187d9
MediaSearch is an alternative, media-focused way to display search results.
While not strictly required, we suggest installing these dependencies to enhance the media search experience.
The following MediaWiki extensions are recommended:
If you have a Wikibase repository, we strongly recommend also installing these extensions to allow more data to be used to enhance the search results:
After the extensions listed above are set up properly, enable the extension by adding wfLoadExtension( 'MediaSearch' ); along with the required config variables to LocalSettings.php.
You might need to run composer install in the extension directory, or in the root directory of your MediaWiki installation if you are using a setup that merges all extension's dependencies into MediaWiki's vendor directory.
Extension configuration variables are sets of key-value pairs. They are documented in more detail in extension.json. Config variables should be added to LocalSettings.php. The following config options are available for this extension:
// External entity search base URI (for autocomplete suggestions, optional) // Leave blank/default (empty string) to use local API. // To disable autocomplete suggestions completely, set to null. $wgMediaSearchExternalEntitySearchBaseUri = 'https://www.wikidata.org/w/api.php'; // URI for getting search results from production during local development. // If this is set, search API calls will be made to this URI. Left blank, // search results will be retrieved from the local API by default. $wgMediaSearchExternalSearchUri = 'https://commons.wikimedia.org/w/api.php';
As much as possible, we default to the Vue Style Guide.
For now, we are not using full single-file components because we need to be able to compile Less separately so it can be included immediately before the app loads to style the PHP UI.
Since Wikimedia UI base variables aren't in core, we require them as a package dependency, then use a shell script to copy them to the lib directory. To update the base variables, require the new version in package.json and install it, then run npm run build-lib to copy the updated file into lib. Commit the updated files.
We're including the base variables in our custom variables file, resources/mediasearch-variables.less. To use them in other files, include mediasearch-variables.less rather than directly including the base file itself.
The CSS class name prefix sdms should be used for extension-level components. sd should be used for base components to keep them extension-agnostic, in case we decide to pull them out into a separate library.
This extension includes a front-end test suite powered by the Jest framework. The tests also make extensive use of the official Vue.js testing library.
For more information about testing Vue code in MediaWiki, please consult the guide here.
At runtime, our JS code relies on a number of objects in the global MediaWiki JS environment. Some of these features need to be mocked during testing. The jest.setup.js file is the best place for mocks that are needed in lots of places. Individual test files can provide additional mocks or override what already exists if more specific mocks are needed.
To run unit tests locally, use the following commands:
# install all required dependencies npm install # run all linters and front-end tests npm run test # run only the front-end unit tests by themselves npm run test:unit