1
0
Fork 0

Clarify custom installer names/interfaces

"i.e." is an abbreviation for "id est", meaning "that is". The intention here is probably "e.g.", "exempli gratia", meaning "for example".

Also gave non-`Composer\` example path and added the name of the interface an installer should implement (it's mentioned later in the article, but it's useful to mention it early).
pull/1693/head
David Zülke 2013-03-13 16:39:22 +02:00
parent e69a05949b
commit d693bdf3bc
1 changed files with 2 additions and 5 deletions

View File

@ -55,10 +55,7 @@ package that has the [type][1] `composer-installer`.
A basic Installer would thus compose of two files:
1. the package file: composer.json
2. The Installer class, i.e.: `Composer\Installer\MyInstaller.php`
> **NOTE**: _The namespace does not need to be `Composer\Installer`, it must
> only implement the right interface._
2. The Installer class, e.g.: `My\Project\Composer\Installer.php`, containing a class that implements `Composer\Installer\InstallerInterface˚.
### composer.json
@ -159,4 +156,4 @@ different installation path.
[1]: ../04-schema.md#type
[2]: ../04-schema.md#extra
[3]: https://github.com/composer/composer/blob/master/src/Composer/Installer/InstallerInterface.php
[4]: https://github.com/composer/composer/blob/master/src/Composer/Installer/LibraryInstaller.php
[4]: https://github.com/composer/composer/blob/master/src/Composer/Installer/LibraryInstaller.php