-
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
fix(specs): multiple clients fixes #3971
Conversation
✔️ 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.
✅
@@ -109,7 +109,7 @@ baseGetApiKeyResponse: | |||
createdAt: | |||
$ref: '../../../../common/responses/common.yml#/createdAtTimestamp' | |||
required: | |||
- key | |||
- value |
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.
weird that redocly doesn't warn about that, I'm sure we have the same somewhere else
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.
I was shocked too idk how it went through?
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.
actually there are some warnings like Component: "attributeToUpdate" is never used.
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.
ah in the warnings we silence? I'll check that
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.
🆗
Co-authored-by: Clément Vannicatte <vannicattec@gmail.com>
algolia/api-clients-automation#3971 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com>
algolia/api-clients-automation#3971 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com>
algolia/api-clients-automation#3971 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com>
algolia/api-clients-automation#3971 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com>
algolia/api-clients-automation#3971 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com>
algolia/api-clients-automation#3971 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com>
algolia/api-clients-automation#3971 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com>
algolia/api-clients-automation#3971 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com>
algolia/api-clients-automation#3971 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com>
algolia/api-clients-automation#3971 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com>
algolia/api-clients-automation#3971 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com>
🧭 What and Why
🎟 JIRA Ticket: https://algolia.atlassian.net/browse/DI-3071
Changes included:
this pr fixes some of the issues identified in the client testing from @kombucha