-
Notifications
You must be signed in to change notification settings - Fork 21
chore(test): check that the response can contain unknown field #4805
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
✔️ 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.
idk about the swift part but the rest looks wonderful
|
||
// languages that just put the response in a map, there is no strict parsing or types to match. | ||
const isLaxLanguage = (lang: string) => { | ||
return lang === 'dart' || lang === 'javascript' || lang === 'python' || lang === 'php'; |
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.
can this be moved as an option in the tests field of the clients config? I tried to update some scripts to remove those inline conditions where possible, having the json schema there as well helps us better describing things
… (generated) [skip ci] Co-authored-by: Pierre Millot <[email protected]>
…ated) algolia/api-clients-automation#4805 Co-authored-by: algolia-bot <[email protected]> Co-authored-by: Pierre Millot <[email protected]>
🧭 What and Why
Add a test that assert that unknown fields doesn't make the deserialization fail, at the root of the object, or nested in a oneOf inside an array inside a object.