Maks Rafalko
Maks Rafalko
> But the problem is that highly conflicts with current failure transports. Those failure transports are meant to be consumed for manual retry. And this is what I propose to...
Six months later, we are working on another project with RabbitMQ instead of Kafka, and the issue is still there. While this is not yet implemented out of the box,...
this is still a good feature to be added
> #47080 adds a new `FailureMessageEvent` that you can listen to. It would allow any specific handling of such failures. If I'm not mistaken, your PR is for Mailer component...
> Create a Command with each of those data groups and write a Handler that calls the change* method on the aggregate Using such commands are useful when we change...
thanks for your answers > Why not take my example and prepare all those methods for a non-legacy scenario but calling them all in one handler - just like the...
Seems like I found the good suggestion here: http://mattallan.org/2016/rest-and-ddd/ > [...] think about mapping resources to domain actions, not entities. A `PATCH` request usually has a couple of different intentions....
For reference, see * https://github.com/infection/infection/issues/1275#issuecomment-647138464 * https://github.com/infection/infection/issues/1275#issuecomment-647180895 * and not merged PR: https://github.com/infection/include-interceptor/pull/13 I didn't have a chance to finish it or came up with another idea, but this is...
After spending hours trying to fix it on Infection side, I think it will be easier to fix it on this library, making another class that extends `BypassFinals` or just...