-
Notifications
You must be signed in to change notification settings - Fork 49
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
"Package php-http/message-factory is abandoned, you should avoid using it. Use psr/http-factory instead." #244
Comments
i am not sure i understand? PSR-17 is the newer standard, but php-http/message-factory is not the same as PSR-17. if a consumer requires php-http/message-factory, they need it to be installed even though it has been deprecated. if the consumer only requires what is the situation where you see and what would you expect to happen? |
Apparently this was a chain of includes that ended with
Is it possible for |
hm, the symfony http client in version 5.4 does require php-http/message-factory, but only as a develop dependency maybe @nicolas-grekas has an idea why this is being installed and if its correct that php-http/messsage-factory is installed? that said, if this no longer happens with symfony 6, it is probably okay. the factories have been deprecated, but we won't remove the repository, so your code will continue working. |
Although the php-http/message-factory as the require-dev for symfony/http-client v5.4-6.2.x, but actually it is a required package! the nyholm/psr7removed the |
You need to install it in your own deps yes, because you're using an optional feature of symfony/http-client. |
php-http/message-factory is required when using HttplugClient from symfony/http-client before version 6.3. Since v6.3, you can use HttplugClient without installing php-http/message-factory. |
php-http/message-factory
has been deprecated and should be removed.Additionally, the instructions to add
Do not prevent
discovery
from auto-requiringmessage-factory
if composer plugins are enabled.The text was updated successfully, but these errors were encountered: