Catching up with missing commits (not moved to the new branch), Fixing issue #1475: incorrect example in LogProfiles API documentation for CreateOrUpdate, fixing incorrect logProfiles example names.#1481
Conversation
…ng issue Azure#1475: incorrect example in LogProfiles API documentation for CreateOrUpdate, fixing incorrect logProfiles example names.
|
Retry of closed PR #1476. |
vishrutshah
left a comment
There was a problem hiding this comment.
@gucalder Change looks good but I noticed that there was already existing error in of the swagger. It'd great if we can address it in this PR itself. Thanks!
| }, | ||
| "x-ms-examples": { | ||
| "List alert rules": { "$ref": "./examples/deleteLogProfile.json" } | ||
| "Delete log profile": { "$ref": "./examples/deleteLogProfile.json" } |
There was a problem hiding this comment.
seems like this example contains an additional response code that has not been modeled in swagger. Could you please verify?
https://travis-ci.org/Azure/azure-rest-api-specs/jobs/258292847#L657
|
@gucalder ping! Could you please see whether we can fix this as part of this PR. Thanks! |
|
@gucalder Thanks for fixing the example. I see that there is still one more invalid example/swagger model for operation https://travis-ci.org/Azure/azure-rest-api-specs/jobs/260424100#L663 |
|
I do not know how to fix this error reported by Linter: "code": "DefinitionsPropertiesNamesCamelCase", |
|
Those are 6 of the 10 errors. |
|
@gucalder Looks like the rule should not have triggered when there is a odata int eh property name. Would you please open an issue at https://github.com/Azure/azure-openapi-validator/issues and link to Azure/autorest#2064 so that we can get it taken care. Thanks! Secondly, Please also have a look at the build |
|
Issues with the MODE:model PR_ONLY=true fixed. Waiting for the result of the validations. |
|
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: File: AutoRest Linter Guidelines | AutoRest Linter Issues Send feedback and make AutoRest Linter Azure Bot smarter day by day! Thanks for your co-operation. |
vishrutshah
left a comment
There was a problem hiding this comment.
Thanks for fixing the errors. I left one question for you. Let me know what you think.
| }, | ||
| { | ||
| "name": "serviceDiagnosticSettingsResource", | ||
| "name": "parameters", |
There was a problem hiding this comment.
@gucalder May I ask the reason for this change i.e renaming the parameter. Seems like generating new SDK from this swagger would not be backward compatible as parameter name has changed. Can you please provide your thoughts.
There was a problem hiding this comment.
That is because I changed the wrong file... I need to change the example file, not the spec file.
I am on this.
|
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: File: AutoRest Linter Guidelines | AutoRest Linter Issues Send feedback and make AutoRest Linter Azure Bot smarter day by day! Thanks for your co-operation. |
|
Thanks @gucalder for incorporating the feedback. |
|
No modification for AutorestCI/azure-sdk-for-node |
|
No modification for AutorestCI/azure-sdk-for-ruby |
|
No modification for AutorestCI/azure-sdk-for-node |
Catching up with missing commits (not moved to the new branch), Fixing issue #1475: incorrect example in LogProfiles API documentation for CreateOrUpdate, fixing incorrect logProfiles example names.
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information
api-versionin the path should match theapi-versionin the spec).Quality of Swagger