-
Notifications
You must be signed in to change notification settings - Fork 44
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
Federated search added #567
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #567 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 10 10
Lines 689 689
=========================================
Hits 689 689 ☔ View full report in Codecov by Sentry. |
b2749b1
to
d5f6edd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution! Good job on the documentation comment, we should add those for the entire gem.
A few things regarding git:
- Try to write commit messages in imperative sentences
Federated search added
❌
Add federated search
✔️ - Use git rebase to clean up the git history.
If you are new to git or unsure how to do this, feel free to reach out to me.
@@ -16,4 +16,19 @@ | |||
expect(response['results'][0]['estimatedTotalHits']).to eq(0) | |||
expect(response['results'][1]['estimatedTotalHits']).to eq(0) | |||
end | |||
|
|||
it 'does a federated search with two different indexes' do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While this test is sufficient to see that the server has indeed understood that this is a federated search and not a regular multi-search, there should be separate tests to see if the server returns what you would expect under these circumstances.
In addition we should check that limit and offset are sent properly and work as expected.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does that meet your expectations?
da76a89
to
77ed25b
Compare
Commit message rewritten and git rebase executed |
77ed25b
to
83a79c8
Compare
Pull Request
Related issue
Fixes #558
What does this PR do?
PR checklist
Please check if your PR fulfills the following requirements: