You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, i am using your client and so far it ist working great.
However i really need to add a random parameter and value to the request uri. Something like "?parmeter=value" right after the from()-method otherwise the API will not provide every entity i need.
Is there a way to provide custom parameters and values or a quick way to "patch" the generated uri?
the uri i need would look like this
(httpsaddressoftheapi)/(Entityname)?parameter=value&?(selectstatement)....
Ok if found a dirty workaround. I just put the whole requeststring into the from((httpsaddressoftheapi)/(Entityname)?parameter=value&?(selectstatement)....) function.
Defeats the purpose of the Library but i can at least use the other convinience features like toArray() for now.
I also found out that the behaviour of the API i consume is in line with the OData Conventions: 5.2 Custom Query Options
It would be nice if the Library would support this in the future.
The text was updated successfully, but these errors were encountered:
Hi, i am using your client and so far it ist working great.
However i really need to add a random parameter and value to the request uri. Something like "?parmeter=value" right after the from()-method otherwise the API will not provide every entity i need.
Is there a way to provide custom parameters and values or a quick way to "patch" the generated uri?
the uri i need would look like this
(httpsaddressoftheapi)/(Entityname)?parameter=value&?(selectstatement)....
Ok if found a dirty workaround. I just put the whole requeststring into the from((httpsaddressoftheapi)/(Entityname)?parameter=value&?(selectstatement)....) function.
Defeats the purpose of the Library but i can at least use the other convinience features like toArray() for now.
I also found out that the behaviour of the API i consume is in line with the OData Conventions:
5.2 Custom Query Options
It would be nice if the Library would support this in the future.
The text was updated successfully, but these errors were encountered: