Replies: 2 comments 4 replies
-
Beta Was this translation helpful? Give feedback.
0 replies
-
We try to put more focus on REST Client Reactive now. Can you check if it works there? |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
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
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...Beta Was this translation helpful? Give feedback.
All reactions