Hey!

I see that this is your first PR. That is great! Welcome!

Symfony has acontribution guide which I suggest you to read.

In short:

• Always add tests
• Keep backward compatibility (seehttps://symfony.com/bc).
• Bug fixes must be submitted against the lowest maintained branch where they apply (seehttps://symfony.com/releases)
• Features and deprecations must be submitted against the 7.3 branch.

Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change.

When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor!
If this PR is merged in a lower version branch, it will be merged up to all maintained branches within a few days.

I am going to sit back now and wait for the reviews.

Cheers!

Carsonbot

I've already done it in a nodeJS project and it works well in production.

asyncfunctioncreateDelayedQueue(channel,exchange,queue,delay){constdate=newDate().toISOString().split('T')[0];constdelayedQueue=`delay_${exchange}_${queue}_${delay}_${date}`;constdelayedExchange='delays';constbaseExpire=24*60*60*1000;awaitchannel.assertQueue(delayedQueue,{durable:true,arguments:{'x-message-ttl':delay,'x-expires':delay+60*1000+baseExpire,'x-dead-letter-exchange':exchange,'x-dead-letter-routing-key':queue,'x-queue-type':'quorum'}});awaitchannel.bindQueue(delayedQueue,delayedExchange,delayedQueue);return{ delayedQueue, delayedExchange};}

This probably also affect 6.4, right?

This probably also affect 6.4, right?

Yes, that's right

Sorry, I've tried to change the base branch to 6.4 and by mistake it has added automatically the reviewers, feel free to leave 🙏
I come back to point to 7.2, as it add a lot of change to the PR, my fault.

No worries, we can target 6.4 while merging this PR 👍