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
Leverage ResetInterface #193
Comments
IMO, the only thing we could do is creating a new processor in charge of dispatching this event when a message have been consumed. This way, for people using the bundle, they'll be able to stop using some of our actual processors (like Doctrine and... that's all!) in favor of the new one. Do you think it's relevant to do this? |
This is a good idea :) Let's do it. |
Oh no, please do it, it's your idea, I definitively don't want to stole it! :) |
Here we go: symfony/symfony#32418 |
First step done, good job. :) Thanks for your job! ❤️ |
Symfony propose a https://github.com/symfony/contracts/blob/master/Service/ResetInterface.php
I think we could leverage this interface.
I'm thinking about doctrine and monolog.
For exemple, in monolog bundle, we clear eveything on kernel.reset.
Doctrine does the same BTW.
So I think we need to add a dependency on the event dispatcher to be able to dispatch a kernel.reset event after each consumed message.
Thanks to that, we could depreciate some Processors :)
WDYT?
The text was updated successfully, but these errors were encountered: