http-message VS Slim Framework

There is a package within The PHP League that allows validation of an OpenAPI specification: league/openapi-psr7-validator. This package validates requests and responses to the PSR-7 specification.

PSR-7, the standard for requests and responses

Guzzle implements PSR-7: HTTP message interfaces (but apparently not yet PSR-18: HTTP Client, or at least they don't mention it). That means it's possible to use it in third-party libraries/frameworks and easy to replace with similar tools.

The Yii HTTP Application provides the Application::class, as well as the events and handlers needed to interact with HTTP. The package is implemented using PSR-7 and PSR-15 standards.

[PSR Http Message.](https://github.com/php-fig/http-message) This repository holds all interfaces/classes/traits related to [PSR-7](http://www.php-fig.org/psr/psr-7/).

PSR Http Message. This repository holds all interfaces/classes/traits related to PSR-7.

Since the library is designed to be easily integrated with different frameworks, it relies on the usage of PSR-7 compliant HTTP messages. To fulfill this requirement, I'll be using the nyholm/psr7 package.

Sounds good for the future given that PHP-FIG seems uninterested in maintaining the related code repo https://github.com/php-fig/http-message/pull/95

Slim is a micro PHP framework used for web development with 11.7k stars and 2k forks on GitHub. It has a simple and intuitive API development process. It is a micro-framework, meaning you only get a minimum of support for HTTP requests and forwarding requests to appropriate controllers. So the question is, why should you choose a micro-framework? Because it offers you flexibility and high extensibility.

Slim is very lightweight and has a similar API to Express https://github.com/slimphp/Slim

Yes, I've opened a ticket with Slim. I also saw it in a non-slim file (Pimple) so I don't think it is a Slim issue.https://github.com/slimphp/Slim/issues/2160

Sounds like part of Slim's RoutingResults. Which then is pretty much:

Switched from Python to PHP and now using Slim. Very happy with the move so far.

At my day job we needed to develop an API and I've never really tried to build one using vanilla PHP, but instead used frameworks such as CodeIgniter or Slim or just a simple file that would mimic the functionality of an API but not be a proper one. Also we had a requirement that we needed to have full control over the code so we were not supposed to use any of the pre built solutions because of that requirement.