Manual:Composer.json best practices/pl

When creating a composer.json file for your extension/library/etc that will be used inside MediaWiki, here are a few best practices to follow. You should also run composer validate, which will point out schema errors.

Konfiguracja

 * "prepend-autoloader": false. Composer's autoloader is slower than MediaWiki's, and most of the classes being loaded are likely to be found inside MediaWiki, so append the composer autoloader instead of prepending it. See this for some more details.
 * "optimize-autoloader": true. No reason not to optimize.

Dobry przykład: mediawiki/core

Zależności

 * Dependencies should be pinned to a specific version number or sha1 commit if a tag isn't available.
 * For development tools like phpunit or phpcs, "dev-master" or "*" is acceptable.

Dobry przykład: mediawiki/core

Naming
Libraries hosted in Gerrit or by the Wikimedia GitHub account should typically be published under the "wikimedia" namespace (e.g. "wikimedia/cdb", "wikimedia/simplei18n"). The use of the "mediawiki" namespace should be reserved for extensions and other intrinsically MediaWiki related components (bot frameworks, etc). Projects hosted at GitHub under an independent organization are encouraged to adopt a similar convention of an organization namespace to be applied consistently across the libraries published by the group.

Rozszerzenia
Extension names should be be all lowercase with s. For example:


 * Rozszerzanie:WikiEditor --> mediawiki/wiki-editor
 * Rozszerzanie:MassMessage --> mediawiki/mass-message

To make themselves installable, a dependency upon "composer/installers" is needed, and the type needs to be set to "mediawiki-extension".

Dobry przykład: mediawiki/extensions/Bootstrap

Skórki
Mainly the same as extensions, except the type should be "mediawiki-skin". The names should end with a suffix of "-skin".

Good example: mediawiki/skins/Vector

Also extension.json
Extensions and skins register information about themselves using an extension.json or skin.json file. Some metadata fields in these files overlap (discussed in T89456), including
 * and
 * and