feat: reconnect and cancelAll consumers

[luddd3]

Provided that they consumed with the channel wrapper function
consume

[jwalton]

You practically read my mind. I was thinking about doing something almost identical to this. I was also thinking about making it so calls to channelWrapper.assertQueue() would add a setup function that asserts the queue (although that's a little trickier, as it won't work if you're trying to create an { exlusive } queue and get the name of the queue back...)

[jwalton]

What do you think of merging these two sets of options objects into one?

Suggested change

	consumeOptions?: amqplib.Options.Consume;
	consumeOptions?: amqplib.Options.Consume & { prefetch?: number };

[luddd3]

It might read better. I was a little bit torn about this because I couldn't decide if it was better to keep the ordinary consume options separated from the node-amqp-connection-manager specific options or not.

I can rewrite it so we get a feel for your alternative.

[jwalton]

I know what you mean, because this is definitely "cleaner" from how we call into amqplib, but the API is a little weird with two sets of options...

If you do something like:

const { prefetch, ...amqpLibOptions } = options;

you can cleanly extract our "custom" options, and anything extra will get passed down to amqplib, so if amqplib adds extra options we don't have to explicitly add them.

[luddd3]

Ah, you read my mind =)

[luddd3]

You practically read my mind. I was thinking about doing something almost identical to this. I was also thinking about making it so calls to channelWrapper.assertQueue() would add a setup function that asserts the queue (although that's a little trickier, as it won't work if you're trying to create an { exlusive } queue and get the name of the queue back...)

Sounds like a good idea!

[jwalton]

🎉 This PR is included in version 3.6.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[rhsobr]

Thanks for this!