Hey!

Thanks for your PR. You are targeting branch "7.1" but it seems your PR description refers to branch "7.1 for features".
Could you update the PR description or change target branch? This helps core maintainers a lot.

Cheers!

Carsonbot

When using the HandleTrait, the HandlerFailedException just adds noise

why not unwrap from within HandleTrait then?

edit: oh BC -.-, perhaps introduce a new property flag instead 🤔

perhaps introduce a new property flag instead

Will give it a try thanks! The property would only serve as a BC layer so I’m not sure if https://symfony.com/doc/current/contributing/code/bc.html#adding-an-argument-to-a-public-method would apply?

adding new private property to traits is allowed :)

it not sure why it would 'serve as a BC layer', it could be just a new feature

if we think it's the better default, then perhaps deprecating HandleTrait in favor of a new QueryBusTrait is the better way. It would solve ambigious naming, and we could mark the message bus property readonly right away.

I dont like the middleware approach, since it might force users to split their bus into multiple buses. IMHO it breaks the abstraction of $theBus->dispatch($aMessage), and comes with double middleware bookkeeping.

adding new private property to traits is allowed :)

Oh indeed I thought you were talking about a new argument for HandleTrait::handle.

it not sure why it would 'serve as a BC layer', it could be just a new feature

AFAIU we first need a way to make the new behavior opt-in (to keep BC), but then remove the old one. The opt-in mechanism would then only serve as a BC layer.

perhaps deprecating HandleTrait in favor of a new QueryBusTrait is the better way.

Don’t know about that, but QueryBus seems too specific: you could use the HandleTrait to implement a command bus e.g.
Something like SingleHandlingTrait maybe..?

@OskarStark @chalasr FYI I also opened #52952 which is an alternative proposed by @ro0NL I find better. Do you have a preference?

Closing, since there is no traction and a solution is trivial to implement in userland.