-
Notifications
You must be signed in to change notification settings - Fork 14
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
feat(specs): add neuralSearch
options
#1474
Conversation
✅ Deploy Preview for api-clients-automation ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✗ The generated branch has been deleted.If the PR has been merged, you can check the generated code on the |
f099953
to
27d5231
Compare
27d5231
to
36df887
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.
awesome !
@@ -108,6 +108,14 @@ baseSearchResponse: | |||
type: string | |||
description: A url-encoded string of all search parameters. | |||
example: query=a&hitsPerPage=20 | |||
redirect: | |||
type: object | |||
description: This parameter is for internal use only. |
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.
do we want to expose something internal ?
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.
yes because the client is used on the dashboard for internal purposes :/
🧭 What and Why
🎟 JIRA Ticket: https://algolia.atlassian.net/browse/DI-1210
Changes included:
closes #1456
this PR implements the changes made on the JavaScript client to leverage the new NeuralSearch parameters.