-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
ClientKafka and KafkaServer naming conventions become much simpler #5603
Comments
Would you like to create a PR for this issue? |
I find out, I can do it just with one variable as clinetId. More importantly, why Kafka interface is copied in two places. |
Fixed in 7.5.0 |
I'm specifying a group-id and it's appending client and server to it - they need to be the same so why is the library appending values that I didn't specify ? |
Feature Request
Is your feature request related to a problem? Please describe.
"Kafka client and consumer naming conventions can be customized by extending ClientKafka and KafkaServer in your own custom provider and overriding the constructor."
Customizing a name becomes very complex since it can be solved with Kafka options.
Describe the solution you'd like
Adding two string to Kafka options and use them in ServerKafka and ClientKafka. Since those values are optional, there is no drawback but it saves a lot of code and effort.
Teachability, Documentation, Adoption, Migration Strategy
https://github.com/nestjs/nest/blob/master/packages/microservices/interfaces/microservice-configuration.interface.ts
https://github.com/nestjs/nest/blob/master/packages/microservices/client/client-kafka.ts
https://github.com/nestjs/nest/blob/master/packages/microservices/server/server-kafka.ts
What is the motivation / use case for changing the behavior?
I am using Kafka as my backbone of event-driven microservice and I use '_' instead of '-' in the patterns.
The text was updated successfully, but these errors were encountered: