-
Notifications
You must be signed in to change notification settings - Fork 17
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
docs(specs): Review OpenAPI Search API (dictionary operations) #1700
docs(specs): Review OpenAPI Search API (dictionary operations) #1700
Conversation
✅ Deploy Preview for api-clients-automation ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✗ The generated branch has been deleted.If the PR has been merged, you can check the generated code on the |
af803d7
to
0ad5aec
Compare
Co-authored-by: Kai Welke <kai.welke@algolia.com>
Co-authored-by: Kai Welke <kai.welke@algolia.com>
Co-authored-by: Kai Welke <kai.welke@algolia.com>
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.
Good for final review by API clients team.
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.
perfect4!
🧭 What and Why
This is one of several PRs addressing the Search API.
This PR reviews just the dictionary operations of the Search API.
Questions and notes
setDictionarySettings
Plurals and compounds are part of the
standardEntries
object but only stop words are supported by the API call. Should the OAS change?🎟 JIRA Ticket: DOC-1107
Changes included:
Changes to summary, description and examples
🧪 Test