We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hey David,
Quick question - is this somehow achievable using the generated client:
So desired HTTP request form:
{serviceUri}/odata/Constructions(1296481)....
OData generated client by your generator produces:
{serviceUri}/odata/Constructions/1296481/....
For the invocation looking like this:
ugkkClient.constructions(id).select("Id").expand(...)...
It seems that OData standard itself implicitly goes with the 1st form: link (see step 2)
Am I doing something wrong here?
Thank you!
The text was updated successfully, but these errors were encountered:
Found a way how to configure the PathStyle.
HttpService httpService = new ApacheHttpClientHttpService(new Path(ugkkAPIUrl, PathStyle.IDENTIFIERS_IN_ROUND_BRACKETS), this::createClient, (url, m) -> m);
B.
Sorry, something went wrong.
Yep, that looks like it. This is similar (and shows setting of PathStyle):
https://github.com/davidmoten/odata-client#how-to-create-a-client-for-your-odata-service-non-microsoft-api-with-bearer-tokens
No branches or pull requests
Hey David,
Quick question - is this somehow achievable using the generated client:
So desired HTTP request form:
{serviceUri}/odata/Constructions(1296481)....
OData generated client by your generator produces:
{serviceUri}/odata/Constructions/1296481/....
For the invocation looking like this:
ugkkClient.constructions(id).select("Id").expand(...)...
It seems that OData standard itself implicitly goes with the 1st form: link (see step 2)
Am I doing something wrong here?
Thank you!
The text was updated successfully, but these errors were encountered: