public-mirrors
/
composer
mirror of https://github.com/composer/composer
1
0
Fork 0
Code

Link to semver version constraint tester

pull/3935/head
Hannes Van De Vreken 2015-04-14 09:21:48 +02:00
parent 4d134ce8a2
commit 93f73ecc8c
1 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/01-basic-usage.md
View File

@ -45,7 +45,7 @@ smaller decoupled parts.
### Package Versions ### Package Versions
In the previous example we were requiring version `1.0.*` of monolog. This In the previous example we were requiring version [`1.0.*`](http://semver.mwl.be/#?package=monolog%2Fmonolog&version=1.0.*) of monolog. This
means any version in the `1.0` development branch. It would match `1.0.0`, means any version in the `1.0` development branch. It would match `1.0.0`,
`1.0.2` or `1.0.20`. `1.0.2` or `1.0.20`.
@ -94,6 +94,13 @@ so using [stability flags](04-schema.md#package-links). To change that for all
packages instead of doing per dependency you can also use the packages instead of doing per dependency you can also use the
[minimum-stability](04-schema.md#minimum-stability) setting. [minimum-stability](04-schema.md#minimum-stability) setting.
### Test version constraints
You can test version constraints using [semver.mwl.be](http://semver.mwl.be). Fill in
a package name and it will autofill the default version constraint which Composer would add
to your `composer.json` file. You can adjust the version constraint and the tool will highlight
all releases that match.
## Installing Dependencies ## Installing Dependencies
To fetch the defined dependencies into your local project, just run the To fetch the defined dependencies into your local project, just run the