Skip to content

Conversation

@yuqi2
Copy link

@yuqi2 yuqi2 commented May 3, 2018

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

Yuqi Zhang and others added 6 commits April 3, 2018 14:27
@AutorestCI
Copy link

AutorestCI commented May 3, 2018

Automation for azure-libraries-for-java

Nothing to generate for azure-libraries-for-java

@AutorestCI
Copy link

AutorestCI commented May 3, 2018

Automation for azure-sdk-for-node

Nothing to generate for azure-sdk-for-node

@AutorestCI
Copy link

AutorestCI commented May 3, 2018

Automation for azure-sdk-for-python

A PR has been created for you:
Azure/azure-sdk-for-python#2526

@AutorestCI
Copy link

AutorestCI commented May 3, 2018

Automation for azure-sdk-for-go

A PR has been created for you:
Azure/azure-sdk-for-go#1784

@marstr
Copy link
Member

marstr commented May 3, 2018

Commits up to b2a473c have been reviewed and approved in: https://github.com/Azure/azure-rest-api-specs-pr/pull/440

edit: spelling

@yuqi2
Copy link
Author

yuqi2 commented May 3, 2018

@marstr @jianghaolu Here attach the the Approval from the PR in private branch : https://github.com/Azure/azure-rest-api-specs-pr/pull/440

@marstr marstr force-pushed the AzureMapsResourceProvider branch from f36b06d to b95d339 Compare May 4, 2018 21:28
@azuresdkciprbot
Copy link

AutoRest linter results for SDK Related Validation Errors/Warnings

These errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns.

File: specification/maps/resource-manager/readme.md

⚠️2 new Warnings.(2 total)
Code Id Source Message
PostOperationIdContainsUrlVerb R2066 Link OperationId should contain the verb: 'moveresources' in:'Accounts_Move'. Consider updating the operationId
PutRequestResponseScheme R2017 Link A PUT operation request body schema should be the same as its 200 response schema, to allow reusing the same entity between GET and PUT. If the schema of the PUT request body is a superset of the GET response body, make sure you have a PATCH operation to make the resource updatable. Operation: 'Accounts_CreateOrUpdate' Request Model: 'MapsAccountCreateParameters' Response Model: 'MapsAccount'
0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@azuresdkciprbot
Copy link

AutoRest linter results for ARM Related Validation Errors/Warnings

These errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns.

File: specification/maps/resource-manager/readme.md

⚠️0 new Warnings.(0 total)
0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

1 similar comment
@azuresdkciprbot
Copy link

AutoRest linter results for ARM Related Validation Errors/Warnings

These errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns.

File: specification/maps/resource-manager/readme.md

⚠️0 new Warnings.(0 total)
0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@azuresdkciprbot
Copy link

AutoRest linter results for SDK Related Validation Errors/Warnings

These errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns.

File: specification/maps/resource-manager/readme.md

⚠️2 new Warnings.(2 total)
Code Id Source Message
PostOperationIdContainsUrlVerb R2066 Link OperationId should contain the verb: 'moveresources' in:'Accounts_Move'. Consider updating the operationId
PutRequestResponseScheme R2017 Link A PUT operation request body schema should be the same as its 200 response schema, to allow reusing the same entity between GET and PUT. If the schema of the PUT request body is a superset of the GET response body, make sure you have a PATCH operation to make the resource updatable. Operation: 'Accounts_CreateOrUpdate' Request Model: 'MapsAccountCreateParameters' Response Model: 'MapsAccount'
0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@marstr marstr force-pushed the AzureMapsResourceProvider branch from b95d339 to b2a473c Compare May 4, 2018 21:32
@azuresdkciprbot
Copy link

AutoRest linter results for ARM Related Validation Errors/Warnings

These errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns.

File: specification/maps/resource-manager/readme.md

⚠️0 new Warnings.(0 total)
0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@azuresdkciprbot
Copy link

AutoRest linter results for SDK Related Validation Errors/Warnings

These errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns.

File: specification/maps/resource-manager/readme.md

⚠️2 new Warnings.(2 total)
Code Id Source Message
PostOperationIdContainsUrlVerb R2066 Link OperationId should contain the verb: 'moveresources' in:'Accounts_Move'. Consider updating the operationId
PutRequestResponseScheme R2017 Link A PUT operation request body schema should be the same as its 200 response schema, to allow reusing the same entity between GET and PUT. If the schema of the PUT request body is a superset of the GET response body, make sure you have a PATCH operation to make the resource updatable. Operation: 'Accounts_CreateOrUpdate' Request Model: 'MapsAccountCreateParameters' Response Model: 'MapsAccount'
0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@jianghaolu jianghaolu merged commit 10e2389 into master May 4, 2018
@vladbarosan vladbarosan deleted the AzureMapsResourceProvider branch November 7, 2018 19:36
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.

6 participants