Repository files navigation

A set of abstractions extracted out of the Symfony components.

Can be used to build on semantics that the Symfony components proved useful - andthat already have battle tested implementations.

• contracts are split by domain, each into their own sub-namespaces;
• contracts are small and consistent sets of PHP interfaces, traits, normativedocblocks and reference test suites when applicable;
• all contracts must have a proven implementation to enter this repository;
• they must be backward compatible with existing Symfony components.

Packages that implement specific contracts should list them in the "provide"section of their "composer.json" file, using thesymfony/*-implementationconvention (e.g."provide": { "symfony/cache-implementation": "1.0" }).

The abstractions in this package are useful to achieve loose coupling andinteroperability. By using the provided interfaces as type hints, you are ableto reuse any implementations that match their contracts. It could be a Symfonycomponent, or another one provided by the PHP community at large.

Depending on their semantics, some interfaces can be combined with autowiring toseamlessly inject a service in your classes.

Others might be useful as labeling interfaces, to hint about a specific behaviorthat could be enabled when using autoconfiguration or manual service tagging (orany other means provided by your framework.)

When applicable, the provided contracts are built on top of PHP-FIG's PSRs. Butthe group has different goals and different processes. Here, we're focusing onproviding abstractions that are useful on their own while still compatible withimplementations provided by Symfony. Although not the main target, we hope thatthe declared contracts will directly or indirectly contribute to the PHP-FIG.

• Documentation
• Contributing
• Report issues andsend Pull Requestsin themain Symfony repository