Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
openapi-psr7-validator
It validates PSR-7 messages (HTTP request/response) against OpenAPI specifications
Symfony implements it
Laravel as well
PHP-DI, which you made, also
Pimple doesn't implement it, but instead provides a separate PSR-11 compliant implementation
That is why I created my minimal view framework Fram. Fram can work independently or together with legacy code and still maintain full control to make it easier to modernize old code bases. I recently added PSR-11 support to it, the container is only called on one occasion, when instantiating the view, so $container->get(...) it is all that it is required.
Even in other cases like in Bref that can be useful to integrate with your favorite framework. All in all, I think PSR-11 is useful, just not as user-facing as PSR-3 or some others.
I have minor issues with the PSR-11 interface due to it not being capable of strong typing on the variables... And yet my framework (https://github.com/feastframework/framework) uses it. It's nice to have that layer of flexibility. Admittedly, I pissed a few people off by just throwing the interface in my codebase but whatevs 😂
And, imagine my surprise, even a Symfony-dedicated lib that does the same under the hood: https://github.com/thephpleague/openapi-psr7-validator