Document arguments for custom commands
Custom commands support the same pattern to pass arbitrary arguments like the "run-script" Composer command.pull/6880/head
parent
ed20b3b4f6
commit
4721a7c2c8
|
@ -210,6 +210,10 @@ simply running `composer test`:
|
||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
|
Similar to the `run-script` command you can give additional arguments to scripts,
|
||||||
|
e.g. `composer test -- --filter <pattern>` will pass `--filter <pattern>` along
|
||||||
|
to the `phpunit` script.
|
||||||
|
|
||||||
> **Note:** Before executing scripts, Composer's bin-dir is temporarily pushed
|
> **Note:** Before executing scripts, Composer's bin-dir is temporarily pushed
|
||||||
> on top of the PATH environment variable so that binaries of dependencies
|
> on top of the PATH environment variable so that binaries of dependencies
|
||||||
> are easily accessible. In this example no matter if the `phpunit` binary is
|
> are easily accessible. In this example no matter if the `phpunit` binary is
|
||||||
|
|
Loading…
Reference in New Issue