Browse Source

Merge pull request #3935 from hannesvdvreken/patch-3

Link to semver version constraint tester
Jordi Boggiano 10 years ago
parent
commit
467f82fc15
1 changed files with 8 additions and 1 deletions
  1. 8 1
      doc/01-basic-usage.md

+ 8 - 1
doc/01-basic-usage.md

@@ -45,7 +45,7 @@ smaller decoupled parts.
 
 ### 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`,
 `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
 [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
 
 To fetch the defined dependencies into your local project, just run the