-
**Is your feature request related to a problem? Please describe.**
It may cause transitivity issues when the project using / requiring this library also needs another version of Guzzle Http Client.
…
-
I know this library is intended to be a "pure" implementation of PSR-7 and its related PSRs. However, that means it also supports PSR-15 and PSR-17. What about PSR-13?
PSR-13 isn't strictly about…
Crell updated
1 month ago
-
Explain Problem Details support for Mezzio/PSR-17.
Again, a hidden gem that can simplify API error reporting tremendously.
-
I've been looking at PSR-18 implementations, and this looks like exactly the sort of thing I was hoping for :-)
My only issue is the dependency on a specific PSR-7 implementation.
Would you cons…
-
As [suggested on Twitter](https://twitter.com/thephpleague/status/962348828413366272), I'm opening a new issue to ask reconsidering #538.
The pros of using http-plug:
- You don't need to handle …
-
Instead of passing in a response object the `JsonApi` class should use a `HttpFactoryInterface` to generate the response if and when it is needed.
This will break backwards compatibility and will r…
-
## Feature Request
| Q | A |
|-------------|--------|
| Package | no |
| New Feature | no |
| BC Break | yes/no |
## Introduction
League uri packages are mad…
-
Hi @mcustiel,
Like for the client, I think you should use more abstraction. Explicitly require guzzle (for the client) or Laminas (for the common) might produce conflicts.
PSR-17 introduce factory…
-
At some point we should make sure we are implementing these compliance definitions:
* https://www.php-fig.org/psr/psr-7/
* https://www.php-fig.org/psr/psr-17/
-
## What/Why
### What are you proposing?
I've developed an OpenSearch plugin for my project (https://github.com/Elgg/Elgg). While trying to update my plugin I ran into a dependency conflict.
My pr…