Skip to content

Conversation

@ankushbindlish2
Copy link
Member

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

  • The title of the PR is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
  • Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
  • If applicable, the PR references the bug/issue that it fixes.
  • Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

@AutorestCI
Copy link

AutorestCI commented Jun 11, 2018

Automation for azure-libraries-for-java

The initial PR has been merged into your service PR:
AutorestCI/azure-libraries-for-java#252

@AutorestCI
Copy link

AutorestCI commented Jun 11, 2018

Automation for azure-sdk-for-python

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-python#2734

@AutorestCI
Copy link

AutorestCI commented Jun 11, 2018

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@AutorestCI
Copy link

AutorestCI commented Jun 11, 2018

Automation for azure-sdk-for-node

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-node#2985

@AutorestCI
Copy link

AutorestCI commented Jun 11, 2018

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

"type": "string"
}
}

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to give this a more descriptive name? E.g. 'StorageSyncError'

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

resolved

"info": {
"title": "Microsoft Storage Sync",
"description": "Microsoft Storage Sync Service API",
"version": "2017-06-05-preview"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you add the client name here? Something like:

"x-ms-code-generation-settings": {
      "name": "StorageSyncClient" or "StorageSyncManagementClient"
 }

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

resolved

"ResourceProvider",
"Operations"
],
"operationId": "OperationGet_list",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The operation ID here should just be "Operations_List"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

resolved

"type": "string"
}
}

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can use the x-ms-client-name extension to rename this for a better developer experience:

"x-ms-client-name": "pauseWaitForSyncDrainTimePeriodInSeconds"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"pauseWaitForSyncDrainTimePeriodInSeconds": {
"type": "integer",
"description": "Pre Restore pause wait for sync drain time period in seconds."
"x-ms-client-name": "pauseWaitForSyncDrainTimePeriodInSeconds"
}

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

resolved

"type": "string"
}
}

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Operation ID should be in the format group_verb. So this should be changed to:
"operationId": "Workflows_abort"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Resolved. Workflows_Abort

"tags": [
"StorageSyncServices Resource"
],
"operationId": "StorageSyncServiceByResourceGroupGet_list",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Operation ID should be in the format "group_verb". So this should be changed to something like:
"operationId": "StorageSyncServices_ListByResourceGroup"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

resolved

"tags": [
"StorageSyncServices Resource"
],
"operationId": "StorageSyncServiceGet_ListBySubscription",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Operation ID should be in the format "group_verb". So this should be changed to something like:
"operationId": "StorageSyncServices_ListBySubscription"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

resolved

"tags": [
"SyncGroup Resource"
],
"operationId": "GetSyncGroups_ListByStorageSyncService",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Operation ID should be in the format "group_verb". So this should be changed to something like:
"operationId": "SyncGroups_ListByStorageSyncService"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

resolved

"tags": [
"CloudEndpoint Resource"
],
"operationId": "CloudEndpointsGet_ListBySyncGroup",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Operation ID should be in the format "group_verb". So this should be changed to something like:
"operationId": "CloudEndpoints_ListBySyncGroup"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

resolved

"Actions",
"Backup Restore"
],
"operationId": "CloudEndpointPreBackup_Post",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Operation ID should be in the format "group_verb". So this should be changed to something like:
"operationId": "CloudEndpoints_PreBackup"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

resolved

@annatisch
Copy link
Member

@ankushbindlish2 - thanks for all the updates! With regards to pausewaitforsyncdraintimeperiodinseconds, the name of the property needs to be the same capitalization as the request over the wire. So something like this:

"pausewaitforsyncdraintimeperiodinseconds": {
  "type": "integer",
  "description": "Pre Restore pause wait for sync drain time period in seconds.",
  "x-ms-client-name": "pauseWaitForSyncDrainTimePeriodInSeconds"
}

What this does is it will convert the name to the best language-specific capitalization for the generated SDKs. e.g. for Python, the property will be pause_wait_for_sync_drain_time_period_in_seconds. But the SDK will automatically convert it into the correct pausewaitforsyncdraintimeperiodinseconds when building the request to send over the wire.

"type": "string"
},
{
"name": "body",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this be renamed to something like "parameters"

"type": "string"
},
{
"name": "body",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this be renamed to something like "parameters"

"type": "string"
},
{
"name": "body",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this be renamed to something like "parameters"

"type": "string"
},
{
"name": "body",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this be renamed to something like "parameters"

"type": "string"
},
{
"name": "body",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this be renamed to something like "parameters"

"type": "string"
},
{
"name": "body",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this be renamed to something like "parameters"

"type": "string"
},
{
"name": "body",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this be renamed to something like "parameters"

"type": "string"
},
{
"name": "body",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this be renamed to something like "parameters"

"type": "string"
},
{
"name": "body",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this be renamed to something like "parameters"

},
"headers": {
"x-ms-request-id": {

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this be renamed to something like "parameters"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants