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

Request Params passed to Client through Index and Type #1427

Merged
merged 2 commits into from Dec 21, 2017
Merged

Conversation

@akadko
Copy link
Contributor

@akadko akadko commented Dec 19, 2017

Client's methods for updating and adding document have non-required array argument requestParams which can be used, for example, for specifying a pipeline. I added the same argument to the corresponding methods of Index and Type classes.

@ruflin
Copy link
Owner

@ruflin ruflin commented Dec 19, 2017

Could you add a line to the CHANGELOG? I restart travis as the failure seemed to be unrelated.

@akadko
Copy link
Contributor Author

@akadko akadko commented Dec 19, 2017

Done with CHANGELOG.

@ruflin
Copy link
Owner

@ruflin ruflin commented Dec 20, 2017

@p365labs Not sure if the failure here is a new issue we have on travis?

@ruflin
Copy link
Owner

@ruflin ruflin commented Dec 21, 2017

@akadko Could you rebase on top of master? I just merged #1431

akadko added 2 commits Dec 19, 2017
…ments methods of Type and Index classes. It is passed to Client's methods which already have that parameter
@akadko akadko force-pushed the akadko:master branch from 4cabd3d to 297a3db Dec 21, 2017
@akadko
Copy link
Contributor Author

@akadko akadko commented Dec 21, 2017

@ruflin Done. Thank you for your help!

@ruflin ruflin merged commit cff7136 into ruflin:master Dec 21, 2017
1 check passed
1 check passed
continuous-integration/travis-ci/pr The Travis CI build passed
Details
@ruflin
Copy link
Owner

@ruflin ruflin commented Dec 21, 2017

@akadko Thanks, merged. Normally I would ask for some tests but I think here it's pretty straight forward as it uses existing methods. If you get some time to add tests in a follow up PR I definitively wont say no ;-)

@akadko
Copy link
Contributor Author

@akadko akadko commented Dec 22, 2017

@ruflin Yes, I should and I will, of course :-). Sorry I had no enough time before

@ruflin
Copy link
Owner

@ruflin ruflin commented Dec 27, 2017

@akadko Great to hear, looking forward to it.

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

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.