Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(rabbitmq): publish using ChannelWrapper #678

Merged
merged 1 commit into from
Jan 16, 2024

Conversation

ttshivers
Copy link
Contributor

Publish messages using the ChannelWrapper instead of the raw ConfirmChannel to take advantage of the reliability features of amqp-connection-manager.

BREAKING CHANGE: This changes the behavior of throwing connection related errors

re #673

Publish messages using the ChannelWrapper instead of the raw ConfirmChannel to take advantage of the
reliability features of  `amqp-connection-manager`.

BREAKING CHANGE: This changes the behavior of throwing connection related errors

re golevelup#673
@underfisk
Copy link
Contributor

@ttshivers I love this change, reduces quite some boilerplate. My only concern is if this will work as intended for existing applications. If our test coverage is enough then I'm happy to include this as part of the next major with amq v4

@underfisk underfisk merged commit 8962eed into golevelup:master Jan 16, 2024
3 checks passed
@ttshivers
Copy link
Contributor Author

I looked over the test coverage and it seems sufficient to ensure that messages are still getting published properly now using the channel wrapper instead.

@underfisk
Copy link
Contributor

I looked over the test coverage and it seems sufficient to ensure that messages are still getting published properly now using the channel wrapper instead.

Alright, thanks!

@ttshivers ttshivers deleted the feat/publish-ChannelWrapper branch January 20, 2024 23:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants