-
Notifications
You must be signed in to change notification settings - Fork 48
Support custom agents #354
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
Conversation
alallema
left a comment
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.
LGTM! 🌯
| expect(index.options).to eq(options.merge({ convert_body?: true })) | ||
|
|
||
| expect(MeiliSearch::Index).to receive(:get).with( | ||
| "#{URL}/indexes/options", |
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.
A bit confusing to call the index options, it looks like a route name and not a resource indexes/options.
But a part for that the test is good!
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.
Agreed, I'll generate an issue to handle that plus a way to randomize the indexes names as we do in the rails :)
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.
Issue created! #355
|
bors merge |
179: Feature/Analytics r=brunoocasali a=brunoocasali Merge after meilisearch/meilisearch-ruby#354 With both PRs, we can send a custom header with the name of this gem according to meilisearch/integration-guides#150. Co-authored-by: Bruno Casali <[email protected]>
Related to meilisearch/integration-guides#150 take #2
We will use this door to send information from the Rails gem.