Skip to content
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

fix: buzz client instantiation using deprecated Message Factory Discovery #250

Merged
merged 2 commits into from
Jul 11, 2023

Conversation

mnavarrocarter
Copy link
Contributor

Fixes the instantiation of Buzz client to use the new Psr17FactoryDiscovery instead of the deprecated MessageFactoryDiscovery.

Q A
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Related tickets none
Documentation none
License MIT

What's in this PR?

Change Buzz instantiator from the deprecated MessageFactoryDisvovery to the new Psr17FactoryDiscovery.

Why?

The Buzz Instantiator was using the deprectaed MessageFactoryDiscovery and this was causing an exception when attempting to instantiate Buzz using nyholm/psr7. Changed to the more modern Psr17FactoryDiscovery that does find nyholm/psr7 for Buzz.

Example Usage

Noop

Checklist

  • Updated CHANGELOG.md to describe BC breaks / deprecations | new feature | bugfix
  • Documentation pull request created (if not simply a bugfix)

Fixes the instantiation of Buzz client to use the new `Psr17FactoryDiscovery` instead of the deprecated `MessageFactoryDiscovery`.
Copy link
Contributor

@dbu dbu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we seem to not have an installation test with buzz but checking the code, the client accepts both factories since 1.0.0

@dbu dbu merged commit 19db1df into php-http:1.x Jul 11, 2023
29 of 30 checks passed
@dbu
Copy link
Contributor

dbu commented Jul 11, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants