[ADLA - ADLS] - Adding existing account APIs that are missing in Swagger#1807
[ADLA - ADLS] - Adding existing account APIs that are missing in Swagger#1807anuchandy merged 3 commits intoAzure:currentfrom
Conversation
anuchandy
left a comment
There was a problem hiding this comment.
@ro-joowan, overall looks good, added some minor feedback, please take a look.
Given that you are just adding existing APIs to the swagger, I am assuming these APIs are approved by ARM review board, right?
There was a problem hiding this comment.
In order to be consistent with tag, operationId naming convention, use tag as Accounts and operationId as Accounts_CheckNameAvailability.
There was a problem hiding this comment.
For this one I would like to leave as is for this PR because we currently have existing APIs for "Account_Get", "Account_Create", etc. We will make the fix to "Accounts" in an upcoming API version, 2017-10-01, which has other breaking changes -- as we would like to bundle the breaking changes together.
There was a problem hiding this comment.
tags -> Locations, operationId -> Locations_GetCapability
There was a problem hiding this comment.
Fixed -- thank you!
There was a problem hiding this comment.
tags -> Locations, operationId -> Locations_List
There was a problem hiding this comment.
Fixed -- thank you!
There was a problem hiding this comment.
Account ->Accounts, Account_CheckNameAvailability -> Accounts_CheckNameAvailability
There was a problem hiding this comment.
For this one I would like to leave as is for this PR because we currently have existing APIs for "Account_Get", "Account_Create", etc. We will make the fix to "Accounts" in an upcoming API version, 2017-10-01, which has other breaking changes -- as we would like to bundle the breaking changes together.
There was a problem hiding this comment.
Fixed -- thank you!
There was a problem hiding this comment.
Fixed -- thank you!
* Added the following existing APIs * Account_CheckNameAvailability * Location_GetCapability * Operation_List * Successfully tested these APIs by generating the C# SDK and executing them * Added example files for these APIs
98fca31 to
6c0a28b
Compare
|
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: File: AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback Thanks for your co-operation. |
|
@anuchandy, These APIs that I am adding were requested by the ARM team for us to add and other services have these exact APIs already. Thank you! |
|
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: File: AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback Thanks for your co-operation. |
1 similar comment
|
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: File: AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback Thanks for your co-operation. |
|
@anuchandy, Also, could you please provide a link where it says that we should use {plural}_{verb}? This was a question we had internally, and the link would be a helpful reference for us in the future. |
|
@ro-joowan sorry this is not documented. I checked with few reviewers, this is not a hard requirement but nice to have a consistency. Some of the reason for choosing plural are -
|
|
@anuchandy Thank you for that. Can we proceed with the merge? |
|
@ro-joowan sure, merging.. |
|
No modification for AutorestCI/azure-sdk-for-node |
Changing the hot readonly memory props to bool...
Added the following existing APIs
Successfully tested these APIs by generating the C# SDK and executing them
Added example files for these APIs
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