-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Add support for sending query params as using a Map in Reactive Rest Client #24783
Conversation
if (componentType == null) { | ||
componentType = DotNames.OBJECT.toString(); | ||
if (isMap(type, index)) { | ||
var resolvesTypes = resolveMapTypes(type, index, jandexMethod); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just a note, usage of Map.Entry here feels weird to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I personally use it all the time because Java doesn't have something like Tuple2
. If you want, I can replace it with a custom class
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, no need to replace it. Maybe some day we could add some simplistic smallrye project, or something inside Quarkus, that would have tuples.
Reactive Rest Client newly supports ([Quarkus PR 24783](quarkusio/quarkus#24783)) passing a query parameters as a map. This is very useful when user don't know query parameters in advance. Feature details can be found in a [TP here](quarkus-qe/quarkus-test-plans#82). Test covers situation when query parameters are of primitive type, Java class or an array (supported by `MultivaluedMap`) and more than one formal parameter is annotated with `@RestQuery`.
Reactive Rest Client newly supports ([Quarkus PR 24783](quarkusio/quarkus#24783)) passing a query parameters as a map. This is very useful when user don't know query parameters in advance. Feature details can be found in a [TP here](quarkus-qe/quarkus-test-plans#82). Test covers situation when query parameters are of primitive type, Java class or an array (supported by `MultivaluedMap`) and more than one formal parameter is annotated with `@RestQuery`.
Reactive Rest Client newly supports ([Quarkus PR 24783](quarkusio/quarkus#24783)) passing a query parameters as a map. This is very useful when user don't know query parameters in advance. Feature details can be found in a [TP here](quarkus-qe/quarkus-test-plans#82). Test covers situation when query parameters are of primitive type, Java class or an array (supported by `MultivaluedMap`) and more than one formal parameter is annotated with `@RestQuery`.
Reactive Rest Client newly supports ([Quarkus PR 24783](quarkusio/quarkus#24783)) passing a query parameters as a map. This is very useful when user don't know query parameters in advance. Feature details can be found in a [TP here](quarkus-qe/quarkus-test-plans#82). Test covers situation when query parameters are of primitive type, Java class or an array (supported by `MultivaluedMap`) and more than one formal parameter is annotated with `@RestQuery`. (cherry picked from commit 5d592c7)
Documents: [24783](quarkusio#24783) Reactive Rest Client sending query paramters passed as a `Map`, however I can't see this in documentation. There should be at least reference to this feature.
Documents: [24783](quarkusio#24783) Reactive Rest Client sending query paramters passed as a `Map`, however I can't see this in documentation. There should be at least reference to this feature.
Documents: [24783](quarkusio#24783) Reactive Rest Client sending query paramters passed as a `Map`, however I can't see this in documentation. There should be at least reference to this feature.
Documents: [24783](quarkusio#24783) Reactive Rest Client sending query paramters passed as a `Map`, however I can't see this in documentation. There should be at least reference to this feature. (cherry picked from commit 95157c5)
Resolves: #24764