26
26
27
27
The abstractions in this package are useful to achieve loose coupling and
28
28
interoperability. By using the provided interfaces as type hints, you are able
29
- to reuse any implementation that matches their contracts. It could be a Symfony
29
+ to reuse any implementations that match their contracts. It could be a Symfony
30
30
component, or another one provided by the PHP community at large.
31
31
32
32
Depending on their semantics, some interfaces can be combined with autowiring to
@@ -38,13 +38,11 @@ any other means provided by your framework.)
38
38
39
39
### How is this different from PHP-FIG's PSRs?
40
40
41
- When applicable, the provided contracts are built on top of PHP-FIG's PSRs. We
42
- encourage relying on them and won't duplicate the effort. Still, the FIG has
43
- different goals and different processes. Here, we don't need to seek universal
44
- standards. Instead, we're providing abstractions that are compatible with the
45
- implementations provided by Symfony. This should actually also contribute
46
- positively to the PHP-FIG (of which Symfony is a member), by hinting the group
47
- at some abstractions the PHP world might like to take inspiration from.
41
+ When applicable, the provided contracts are built on top of PHP-FIG's PSRs. But
42
+ the group has different goals and different processes. Here, we're focusing on
43
+ providing abstractions that are useful on their own and are compatible with
44
+ implementations provided by Symfony. While not the main target, we hope that the
45
+ declared contracts will directly or indirectly contribute to the PHP-FIG.
48
46
49
47
### Why isn't this package split into several packages?
50
48
0 commit comments