adding headers and custom ExchangeTypes #47
Merged
Conversation
This file contains hidden or 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
DanielePalaia
force-pushed
the
adding_headers_and_custom_exchange
branch
10 times, most recently
from
605b43d to
5e67fad
Compare
DanielePalaia
force-pushed
the
adding_headers_and_custom_exchange
branch
from
5e67fad to
b790364
Compare
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.
This PR adds support for headers and CustomExchange type.
There is a strage behaviour happening testing the CustomExchange functionality, as it creates a dump when the tests run on the github action (even tough all the tests pass fine).
This is not reproducible anywhere (OSX, Ubuntu ecc...) and the functionality is working good so I removed that test for the moment till we don't understand the root cause.