-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Refactor clientfactory customizer #27653
Refactor clientfactory customizer #27653
Conversation
API changes have been detected in |
API changes have been detected in |
API changes have been detected in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
.../main/java/com/azure/spring/cloud/stream/binder/eventhubs/EventHubsMessageChannelBinder.java
Show resolved
Hide resolved
@@ -225,7 +223,7 @@ private EventHubsTemplate getEventHubTemplate() { | |||
DefaultEventHubsNamespaceProducerFactory factory = new DefaultEventHubsNamespaceProducerFactory( | |||
this.namespaceProperties, getProducerPropertiesSupplier()); | |||
|
|||
clientFactoryCustomizers.forEach(customizer -> customizer.customize(factory)); | |||
producerFactoryCustomizers.forEach(customizer -> customizer.customize(factory)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do we design the interface to accept an argument of abstract type
while in the implementation use its implementation? How about always using the implementation for clarity? By this way, we avoid the is instanceof
judgement then.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should use API instead of impl classes in APIs.
/azp run java - spring - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
According to the API review, this PR will split the
ClientFactoryCustomizer
into two separate factory customizers. https://apiview.dev/Assemblies/Conversation/75bcb52fc5c74dbcaa45847030d90f4b