-
-
Notifications
You must be signed in to change notification settings - Fork 260
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
Wildcard routing stopped working. RabbitMQ #712
Labels
Comments
Andrius0124
pushed a commit
to Andrius0124/nestjs
that referenced
this issue
Mar 24, 2024
Andrius0124
pushed a commit
to Andrius0124/nestjs
that referenced
this issue
Mar 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#567
Regarding the issue above. It seems that it has broken some existing functionality.
Let me give an example:
@RabbitRPC({ routingKey: "USER.UPDATED.#", queue: "someQueue" }) async handleUserUpdated()
if the message is pushed with routingKey "USER.UPDATED.TEST" the handler will never be hit.
The question is, should the wildcards be respected at that point, or is my initial implementation wrong?
PR added
@WonderPanda
The text was updated successfully, but these errors were encountered: