Skip to content
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

Query parameters set through RequestBuilder.queryParam(...) are ignored when using .search #62

Open
braveulysses opened this issue Apr 26, 2016 · 0 comments

Comments

@braveulysses
Copy link
Collaborator

Arbitrary query parameters set via RequestBuilder.queryParam(...) are ignored when used in conjunction with a search via POST.

Adding something like

      service.searchRequest("Users").
          filter(filter).
          queryParam(expectedKey, expectedValue).
          invokePost(UserResource.class);

to EndpointTestCase.testQueryParams() should reproduce this.

Note that there isn't actually an implementation yet. For the client to set these parameters, logic needs to be added to SearchRequestBuilder.invoke(boolean, SearchResultHandler<T>, Class<T>), similar to the existing logic there for handling arbitrary headers. Then, support will need to be added to the server component, in DotSearchFilter, I assume.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant