Support @Encoded for query parameters in REST Client Reactive

[michalszynkiewicz]

Description

From GitHub discussion:

Hello,

I am following this guide https://quarkus.io/guides/rest-client to communicate with a 3rd party API. Overall everything works but there is a small issue I am running with query param.

I am able to set up query param as described in the tutorial. However, I am not able to use the Encoded string as a query param.

For example

I have this endpoint

   @Path("/device")
   @GET
   fun deviceSelect(@QueryParam("\$select")  selectQuery: String): ListOf<DeviceMeta>

Also, the third-party follows the odata conventions.

Now when I pass in a single field into this method, everything works, I get a list with that field.

However, when I put in multiple fields, so something like deviceSelect("name,id"), I run into malformed URL. Basically, the other endpoint is expecting the actual , but our endpoint is passing it with % encoded.

i.e valid: /device?$select=name,id
whats generated: /device?%24select=name%2Cid

I know the third-party API is supposed to handle the encoded inputs but I need a solution while they fix that.

I tried annotating the param, method, and class with @encoded but had no luck...

Implementation ideas

No response

[michalszynkiewicz]

CC @sraturi

[michalszynkiewicz]

I checked that this is doable. OTOH, it may be unsafe in some circumstances, I think.

@geoand @radcortez what do you guys think of supporting @Encoded in the client?

[geoand]

The alternative being that the user needs to setup the proper string manually?

[michalszynkiewicz]

IIUC, curerntly @sraturi is not able to send query params he needs with the client. OTOH, as he points out himself, the server he contacts should support encoded params (it doesn't and that's the problem he's trying to work around).

[geoand]

Yeah, I'm not so sure doing this on the client is correct way to go...

[bboyz269]

We really don't have any saying in 3rd party service implementations ...
Is there any possible point we can intercept to work around?

[geoand]

Not really