-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Missing Error Definitions or References in 9 Swagger Specs #252
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
Comments
Which error codes are you referring to? Please be specific or the issues will be long lived and difficult to determine if they are completely resolved. |
@devigned - if you go to their corresponding REST API specs, then you can see it. I provided some examples in the first comment |
@Azure/adx-autorest-contributors and @Azure/openapi-advisors any thoughts on this issue? |
@devigned Two thoughts, one specific to Search, one general:
|
OAI/OpenAPI-Specification#566 <-- to help follow 3.0 suggestions |
We should have a shared (common) set of schema, a base error should be returned by default (non-success responses) specialized by the error code via a polymorphic discriminator. This will provide the information to specialize the initialized class as well as the to document all of the possible error responses. |
Closing since this is being tracked here - Azure/autorest#1523. |
[ACS,AKS] remove "count" from required fields since it has a default
Missing Error Definitions or References in 9 Swagger Specs
Notification Hubs REST API throws several error codes however its Swagger does not define any of these.
Search REST API throws several error codes however its Swagger does not define any of these.
Azure Active Directory Graph API throws several error codes however its Swagger does not define any of these.
So on and on ...
The text was updated successfully, but these errors were encountered: