Exporting Channel State #4
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey Guys, this is an old PR from streadway, and since we have this "official" fork, I'd still think is a good idea (and I need this haha)
I needed to access the Channel state on a project that I'm participating in. So, I just made the "closed" field public on channel.go in the same way as it is on connection.go. Nothing too fancy, but I think it is important to get the actual status of the channel.
Something that we have on RabbitMQ's client on Python (pika) and .Net (RabbitMQ) and I missed here.
Hope this helps,
Best regards.
Original Pull Request