Merge branch '2.2' into 2.3
commit
e1ab520d64
|
@ -12,7 +12,7 @@ The only good alternative is to define an upper bound on your constraints,
|
|||
which you can increase in a new release after testing that your package is
|
||||
compatible with the new major version of your dependency.
|
||||
|
||||
For example instead of using `>=3.4` you should use `~3.4` which allows all
|
||||
For example instead of using `>=3.4` you should use `^3.4` which allows all
|
||||
versions up to `3.999` but does not include `4.0` and above. The `^` operator
|
||||
works very well with libraries following [semantic versioning](https://semver.org).
|
||||
|
||||
|
|
|
@ -6,7 +6,7 @@
|
|||
"name": {
|
||||
"type": "string",
|
||||
"description": "Package name, including 'vendor-name/' prefix.",
|
||||
"pattern": "^[a-z0-9]([_.-]?[a-z0-9]++)*+/[a-z0-9](([_.]|-{1,2})?[a-z0-9]++)*+$"
|
||||
"pattern": "^[a-z0-9]([_.-]?[a-z0-9]+)*\/[a-z0-9](([_.]|-{1,2})?[a-z0-9]+)*$"
|
||||
},
|
||||
"description": {
|
||||
"type": "string",
|
||||
|
|
|
@ -25,9 +25,9 @@ class ComposerSchemaTest extends TestCase
|
|||
$expectedError = array(
|
||||
array(
|
||||
'property' => 'name',
|
||||
'message' => 'Does not match the regex pattern ^[a-z0-9]([_.-]?[a-z0-9]++)*+/[a-z0-9](([_.]|-{1,2})?[a-z0-9]++)*+$',
|
||||
'message' => 'Does not match the regex pattern ^[a-z0-9]([_.-]?[a-z0-9]+)*/[a-z0-9](([_.]|-{1,2})?[a-z0-9]+)*$',
|
||||
'constraint' => 'pattern',
|
||||
'pattern' => '^[a-z0-9]([_.-]?[a-z0-9]++)*+/[a-z0-9](([_.]|-{1,2})?[a-z0-9]++)*+$',
|
||||
'pattern' => '^[a-z0-9]([_.-]?[a-z0-9]+)*/[a-z0-9](([_.]|-{1,2})?[a-z0-9]+)*$',
|
||||
),
|
||||
);
|
||||
|
||||
|
|
Loading…
Reference in New Issue