fix: buzz client instantiation using deprecated Message Factory Discovery #250
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes the instantiation of Buzz client to use the new
Psr17FactoryDiscovery
instead of the deprecatedMessageFactoryDiscovery
.What's in this PR?
Change Buzz instantiator from the deprecated
MessageFactoryDisvovery
to the newPsr17FactoryDiscovery
.Why?
The Buzz Instantiator was using the deprectaed
MessageFactoryDiscovery
and this was causing an exception when attempting to instantiate Buzz usingnyholm/psr7
. Changed to the more modernPsr17FactoryDiscovery
that does findnyholm/psr7
for Buzz.Example Usage
Noop
Checklist