-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Azure maps resource provider #3007
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
Conversation
* Change Azure Maps to Maps * Azure Maps to Maps * add examples * change file names * add 2018-05-01 * change api-version to 2018-05-01
Automation for azure-libraries-for-javaNothing to generate for azure-libraries-for-java |
Automation for azure-sdk-for-nodeNothing to generate for azure-sdk-for-node |
Automation for azure-sdk-for-pythonA PR has been created for you: |
Automation for azure-sdk-for-goA PR has been created for you: |
|
Commits up to b2a473c have been reviewed and approved in: https://github.com/Azure/azure-rest-api-specs-pr/pull/440 edit: spelling |
|
@marstr @jianghaolu Here attach the the Approval from the PR in private branch : https://github.com/Azure/azure-rest-api-specs-pr/pull/440 |
f36b06d to
b95d339
Compare
AutoRest linter results for SDK Related Validation Errors/WarningsThese 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
|
| 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.
AutoRest linter results for ARM Related Validation Errors/WarningsThese 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
|
1 similar comment
AutoRest linter results for ARM Related Validation Errors/WarningsThese 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
|
AutoRest linter results for SDK Related Validation Errors/WarningsThese 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
|
| 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.
b95d339 to
b2a473c
Compare
AutoRest linter results for ARM Related Validation Errors/WarningsThese 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
|
AutoRest linter results for SDK Related Validation Errors/WarningsThese 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
|
| 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.
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