-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Declaration of Slim\Psr7\Uri::withScheme($scheme) must be compatible with Psr\Http\Message\UriInterface::withScheme(string $scheme): Psr\Http\Message\UriInterface #292
Comments
What version of PSR are you using? |
Thanks for reply. How to check PSR version? |
Also, there is psr/http-message version 2.0. We have 2 psr/http-message packages (one that came with a product we use, the other one came with a particular module of this application, but both of them are, I think, of April 2023). |
I think the problem is that there are no type hints. |
The active package is 2.0. Now the slim/psr7 package lacks function parameter and return hints. |
It's a big problem for us too. For now we have to freeze psr/http-message to version 1.1 although all of our other dependencies (like Symfony and Laminas) allow 2.0. The only dependency still stuck @ 1.1 is Slim. Thankfully, other dependencies also allow version 1 (^1.1 || ^2.0) but it's a matter of time until ^2.0 will be the minimum for a package. This will probably force us to move everything to Symfony, because they would never allow such an old version to rot in their source code for too long. |
Here is a workaround. Shouldn't really be used in production tho. I believe the pipeline is failing.
Originally posted by @clownmeister in #296 (comment) |
This have been fixed in v1.7.0. |
Hello, after updating The psr/http-message to the latest version I have the following error:
Declaration of Slim\Psr7\Uri::withScheme($scheme) must be compatible with Psr\Http\Message\UriInterface::withScheme(string $scheme): Psr\Http\Message\UriInterface.
Will there be an update to Slim\PSR7?
The text was updated successfully, but these errors were encountered: