Closed nathanjrobertson closed 4 weeks ago
thanks foe your pr
This PR introduces a bug.
Constant BeforeProducerPublishMessageEvent::NAME
refers to AMQPEvent::BEFORE_PROCESSING_MESSAGE
instead of having an unique event name. This incorrectly triggers consumer listeners if already exist.
@nathanjrobertson @mihaileu
fixed in #729
Thank you, and apologies for the regression.
Currently, Consumers have events which allow users of the bundle to add custom code. This PR adds this support to Producers as well. Really useful for project specific logging, message format validation, etc.
The only real difference between the Consumer and Producer events is the addition of the
routingKey
field in the Events, as$producer->routingKey
is only set in the case where it is explicitly set, and not in the case wheredefaultRoutingKey
is used. This PR currently works around this by providing that extra field, but it might be better to changeProducer.php
(line 67) from:to
and then removing the extra
routingKey
field from the Events. Happy to take feedback on which way you'd prefer this one go.My use case for this support is message validation prior to publishing.