feat: add support for RabbitMQ mandatory property #145
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
🎉 This PR is included in version 5.5.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces support for RabbitMQ's mandatory property in publishing operations. A new configuration option has been added, allowing developers to specify the behavior of the mandatory property when sending messages through:
When the mandatory property is set to true, if a message cannot be routed to any queue (e.g., because no binding matches the routing key), the RabbitMQ broker will return the message to the producer, showing a log. If set to false (the default behavior), the message is silently discarded.
Providing control over the mandatory property offers an immediate feedback mechanism for routing issues. This is essential in architectures where message delivery is critical and there is a need to proactively detect configuration or topology errors, thus preventing data loss.