Question 1

How to check PHP extension availability with Composition?

Accepted Answer

Use the `has` method with the extension name, like `\Composition::has('ext-mongo')`, as shown in the README. This provides a straightforward way to validate extensions without manual function existence checks.

Question 2

Composition or manual class_exists checks: which is better for dependency validation?

Accepted Answer

Composition is better for standardizing Composer-based checks and reducing code duplication, while manual checks offer more flexibility for non-Composer dependencies. Composition excels in test environments for version-aware validation.

Question 3

Can Composition be used in Symfony or Laravel projects?

Accepted Answer

Yes, since these frameworks typically use Composer, you can integrate Composition for environment checks in tests. However, follow the README advice to avoid overusing it in production code.

Question 4

How to skip PHPUnit tests when a package is missing using Composition?

Accepted Answer

In your test setup, use `if (!\Composition::has('package-name')) { $this->markTestSkipped('Package required'); }` as demonstrated in the README example, ensuring tests run only when dependencies are met.

Question 5

Is Composition compatible with PHP 8.x versions?

Accepted Answer

Yes, Composition can validate PHP versions, so you can use `\Composition::has('php', '^8.0')` to ensure compatibility. Always check the library's own Composer requirements for updates.

Question 6

What are the performance implications of using Composition in production?

Accepted Answer

The README discourages production use, as runtime checks could add overhead. It's best reserved for test suites where environment validation is critical without affecting live performance.

Composer-Composition

What is Composer-Composition?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions