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

[Feature Request]: Be able to define more than one message type for a topic #119

Open
sergioamribeiro opened this issue Apr 4, 2023 · 0 comments
Labels
enhancement New feature or request help wanted Extra attention is needed low priority Low priority issue question Further information is requested

Comments

@sergioamribeiro
Copy link
Contributor

Is your request related to a problem you have?

Yes. We are using an Avro consumer with one topic that consumes more than one contract and we cannot register with the existing method WithMessageType more than 1 contract.

Describe the solution you'd like

The method below should accept more than one message type. The class is RetryDurableDefinitionBuilder

public RetryDurableDefinitionBuilder WithMessageType(Type messageType)
      {
          this.messageType = messageType;
          return this;
      }

Are you able to help bring it to life and contribute with a Pull Request?

No

Additional context

No response

@sergioamribeiro sergioamribeiro added the enhancement New feature or request label Apr 4, 2023
@jdromeiro jdromeiro added the help wanted Extra attention is needed label Apr 27, 2023
@Daniel-C-Dias Daniel-C-Dias added question Further information is requested medium priority Medium priority issue low priority Low priority issue and removed medium priority Medium priority issue labels May 18, 2023
@luispfgarces luispfgarces changed the title [Feature Request]: Be able to define more than one message type for [Feature Request]: Be able to define more than one message type for a topic Aug 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed low priority Low priority issue question Further information is requested
Development

No branches or pull requests

3 participants