-
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
feat(clients): deserialize in e2e and SFFV response #2500
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 |
2500 |
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.
the statusCode assertion has disappeared from the CTS ?
only for endpoints with body assertions since the deserialized object doesn't contain it, but the |
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.
nice
🧭 What and Why
🎟 JIRA Ticket: https://algolia.atlassian.net/browse/DI-1748
Changes included:
We now deserialize responses in the generated models for Python, pydantic would raise an error if it failed
Also fix the search for facet values response which was missing properties