-
Notifications
You must be signed in to change notification settings - Fork 22
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
Introduce response models for operations with application/json payload #25
Comments
Sample payload for aem-healthcheck: |
Sample payload for agents list: |
Sample payload for package filter: |
Sample payload for package service: |
Sample payload for authorizable ID: |
All operations currently pass all responses as string.
While this is useful for xml, html, and plain text payload where processing is handled at the next layer (e.g. ruby_aem), this is not necessarily true for json payload where responses can be modelled at OpenAPI spec.
When the API introduces the model, need to also update ruby_aem to handle the model instead of json parsing.
The text was updated successfully, but these errors were encountered: