Support query parameters to get queues, exchanges, connections and channels #236
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
when initialized directly from an array
michaelklishin
approved these changes
Mar 24, 2021
|
Thank you! |
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.
RabbitMQ Management API supports column selection, sorting, name-based filtering and paging. I need the majority of these features to get queues, specially paging. For completeness, i have decided to do it for the rest of the endpoints that support paging which are exchanges, channels and connections.
There is only one test case that verifies paging.
I had to use Apache URIBuilder because Spring URI encoder class was not properly encoding regular expressions. For instance, characters such as
+or$or parenthesis were not encoded.