-
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
fix(specs): add type: object to 3 schemas #4392
Conversation
Explicit is better than implicit, so this commit adds `type: object` to 3 schemas standardEntries, userData, and source.
💥 Breaking changes detected !!Either this PR or a previous PR not released yet introduced breaking changes, be careful when merging. ✔️ Code generated!
📊 Benchmark resultsBenchmarks performed on the method using a mock server, the results might not reflect the real-world performance.
|
|
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 !
Co-authored-by: Kai Welke <[email protected]>
algolia/api-clients-automation#4392 Co-authored-by: algolia-bot <[email protected]> Co-authored-by: Kai Welke <[email protected]>
algolia/api-clients-automation#4392 Co-authored-by: algolia-bot <[email protected]> Co-authored-by: Kai Welke <[email protected]>
algolia/api-clients-automation#4392 Co-authored-by: algolia-bot <[email protected]> Co-authored-by: Kai Welke <[email protected]>
algolia/api-clients-automation#4392 Co-authored-by: algolia-bot <[email protected]> Co-authored-by: Kai Welke <[email protected]>
algolia/api-clients-automation#4392 Co-authored-by: algolia-bot <[email protected]> Co-authored-by: Kai Welke <[email protected]>
algolia/api-clients-automation#4392 Co-authored-by: algolia-bot <[email protected]> Co-authored-by: Kai Welke <[email protected]>
algolia/api-clients-automation#4392 Co-authored-by: algolia-bot <[email protected]> Co-authored-by: Kai Welke <[email protected]>
algolia/api-clients-automation#4392 Co-authored-by: algolia-bot <[email protected]> Co-authored-by: Kai Welke <[email protected]>
algolia/api-clients-automation#4392 Co-authored-by: algolia-bot <[email protected]> Co-authored-by: Kai Welke <[email protected]>
algolia/api-clients-automation#4392 Co-authored-by: algolia-bot <[email protected]> Co-authored-by: Kai Welke <[email protected]>
algolia/api-clients-automation#4392 Co-authored-by: algolia-bot <[email protected]> Co-authored-by: Kai Welke <[email protected]>
🧭 What and Why
I found some schemas without specified
type
property.3 of them are
type: object
which is probably implied since they had theproperties:
field.1 schema didn't have a type defined which made it
type: any
but it should be a string.This helps with me rendering method parameters etc.
🎟 JIRA Ticket:
Changes included:
Search API
Added
type: object
to:standardEntries
userData
source
(was implied before since all of them had
properties
)Recommend API
Added
type: string
to:facetName
(was unspecified before and rendered in the docs as
type: any
).