Update ReadAny to skip over lists and maps #372
Merged
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.
Addresses #371 enough to at least get the client working again with RabbitMQ 3.13.
For now, this just returns
null
as the value for lists and maps. The project can decide how to correctly handle this, since thex-received-from
message annotation has the following structure:The
x-shoveled
message annotation has the following structure:But since the message annotation of AMQP 1.0 is completely flexible, this client shouldn't lock into just the current value types. Maybe return generic
List<object>
andDictionary<object, object>
?I have a
patch-any-2
branch toward that end, but no tests, and breaking API changes to enable use of the existingMap<>
...