function ComponentsTaggedReleaseTest::providerVersionConstraint

Same name and namespace in other branches
  1. 10 core/tests/Drupal/BuildTests/Composer/Component/ComponentsTaggedReleaseTest.php \Drupal\BuildTests\Composer\Component\ComponentsTaggedReleaseTest::providerVersionConstraint()
  2. 9 core/tests/Drupal/BuildTests/Composer/Component/ComponentsTaggedReleaseTest.php \Drupal\BuildTests\Composer\Component\ComponentsTaggedReleaseTest::providerVersionConstraint()
  3. main core/tests/Drupal/BuildTests/Composer/Component/ComponentsTaggedReleaseTest.php \Drupal\BuildTests\Composer\Component\ComponentsTaggedReleaseTest::providerVersionConstraint()

Highly arbitrary version and constraint expectations.

Return value

array

  • First element is the tag that should be applied to \Drupal::version.
  • Second element is the resulting constraint which should be present in the component core dependencies.

File

core/tests/Drupal/BuildTests/Composer/Component/ComponentsTaggedReleaseTest.php, line 29

Class

ComponentsTaggedReleaseTest
Demonstrate that the Component generator responds to release tagging.

Namespace

Drupal\BuildTests\Composer\Component

Code

public static function providerVersionConstraint() : array {
  return [
    // [Tag, constraint]
'1.0.x-dev' => [
      '1.0.x-dev',
      '1.0.x-dev',
    ],
    '1.0.0-beta1' => [
      '1.0.0-beta1',
      '1.0.0-beta1',
    ],
    '1.0.0-rc1' => [
      '1.0.0-rc1',
      '1.0.0-rc1',
    ],
    '1.0.0' => [
      '1.0.0',
      '^1.0',
    ],
  ];
}

Buggy or inaccurate documentation? Please file an issue. Need support? Need help programming? Connect with the Drupal community.