This must target 7.1 due to feature freeze period

Thank you @javaDeveloperKid.

Can you consider this as a bug fix and backport it to 6.4 😂 (jk)? This exactly something we need in our app, where we migrate maaaany workers using multiple transports (because our AMQP instance uses multiple exchanges). It would be much better to use--all instead of specifying all the transports (receivers) in the CLI command.

Can you consider this as a bug fix and backport it to 6.4 😂 (jk)? This exactly something we need in our app, where we migrate maaaany workers using multiple transports (because our AMQP instance uses multiple exchanges). It would be much better to use--all instead of specifying all the transports (receivers) in the CLI command.

What if you use 7.1 in your app?

composer require symfony/messenger:^7.1

Update: I just realized that there is a7.1 branch but it isn't released yet. It will bereleased in May, then upgrading should work and allow you to use the--all option.

In the meantime, using a commit or the Composer flag@dev for this package may work.

@alexislefebvre Thanks for the feedback, but actually I knew it before☺️. I've added@TODO for migrating to 7.1 when it's available and then we'll use--all. Unfortunately@dev is not suitable for our system, which is too big and too important.

@Wirone Another approach would be to copy past this class from 7.1 branch to your respository and register this in your composer,json. Composer will pick up the first class found in this namespace which will be yours.
When you upgrade to 7.1+ one day, you will just remove this class.

P.S. Remember to check that changes between your 6.4.x locked in your composer.lock and 7.1 branch are only the ones from this PR. If not then decide if it's safe to use it.

FYI: I was able to introduce--all in Symfony 6.4 pretty easily -here's how 😎.