Skip to content

Conversation

jaredmoo
Copy link
Contributor

@jaredmoo jaredmoo commented Feb 25, 2017

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

  • I have read the contribution guidelines.
  • My spec meets the review criteria:
    • The spec conforms to the Swagger 2.0 specification.
    • Validation errors from the Linter extension for VS Code have all been fixed for this spec. (Note: for large, previously checked in specs, there will likely be many errors shown. Please contact our team so we can set a timeframe for fixing these errors if your PR is not going to address them).
    • The spec follows the patterns described in the Swagger good patterns document unless the service API makes this impossible.

Reading "Azure SQL" over and over again is exhausting and gets in the way of understanding the docs.
@azurecla
Copy link

Hi @jaredmoo, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!


It looks like you're working at Microsoft (jaredmoo). If you're full-time, we DON'T require a contribution license agreement.



If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@@ -241,7 +241,7 @@
"items": {
"$ref": "#/definitions/ServerFirewallRule"
},
"description": "The list of Azure SQL server firewall rules for the server."
"description": "The list of server firewall rules for the server."
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you just make it "The list of firewall rules for the server" for this one?

@@ -2,7 +2,7 @@
"swagger": "2.0",
"info": {
"title": "Azure SQL Database API spec",
"description": "Provides create, read, update and delete functionality for Azure SQL resources including servers, databases, elastic pools, recommendations, operations, and usage metrics.",
Copy link
Contributor

Choose a reason for hiding this comment

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

This is the one place I'd like to leave Azure SQL

@@ -241,7 +241,7 @@
"items": {
"$ref": "#/definitions/ServerFirewallRule"
},
"description": "The list of Azure SQL server firewall rules for the server."
"description": "The list of server firewall rules for the server."
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you just make it "The list of firewall rules for the server" for this one?

@@ -2,7 +2,7 @@
"swagger": "2.0",
"info": {
"title": "Azure SQL Database API spec",
"description": "Provides create, read, update and delete functionality for Azure SQL resources including servers, databases, elastic pools, recommendations, operations, and usage metrics.",
Copy link
Contributor

Choose a reason for hiding this comment

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

This is the one place I'd like to leave Azure SQL in

@@ -294,7 +294,7 @@
"Databases"
],
"operationId": "Databases_ListByServer",
"description": "Returns information about an Azure SQL database.",
"description": "Returns information about a database.",
Copy link
Contributor

Choose a reason for hiding this comment

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

I know this isn't your error, but could you put "Returns a list of databases by server."?

@@ -375,7 +375,7 @@
"Servers"
],
"operationId": "Servers_List",
"description": "Returns information about an Azure SQL server.",
"description": "Returns information about a server.",
Copy link
Contributor

Choose a reason for hiding this comment

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

"Returns a list of servers."?

@@ -554,7 +554,7 @@
"Servers"
],
"operationId": "Servers_ListUsages",
"description": "Returns information about Azure SQL server usage.",
"description": "Returns information about server usage.",
Copy link
Contributor

Choose a reason for hiding this comment

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

usages

@@ -943,7 +943,7 @@
"RecommendedElasticPools"
],
"operationId": "RecommendedElasticPools_Get",
"description": "Gets information about an Azure SQL Recommended Elastic Pool.",
"description": "Gets information about an recommended elastic pool.",
Copy link
Contributor

Choose a reason for hiding this comment

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

a recommended

Also restored "Azure SQL Database" wording to doc titles and tweaked list operation descriptions.
@@ -1560,7 +1560,7 @@
"$ref": "#/definitions/Resource"
}
],
"description": "Represents an Azure SQL Recommended Elastic Pool."
"description": "Represents an recommended elastic pool."
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe ctrl+replace 'an recommended'

@@ -1560,7 +1560,7 @@
"$ref": "#/definitions/Resource"
}
],
"description": "Represents an Azure SQL Recommended Elastic Pool."
"description": "Represents an recommended elastic pool."
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe ctrl+replace 'an recommended'

Copy link
Member

@anuchandy anuchandy left a comment

Choose a reason for hiding this comment

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

CI is failing specifically with error "FATAL: Error generating client model: System.InvalidOperationException: Swagger document contains two or more x-ms-enum extensions with the same name 'ServiceObjectiveName' and different values.", please take a look and fix.

@@ -99,7 +99,7 @@
"in": "path",
"required": true,
"type": "string",
"description": "The name of the Azure SQL server firewall rule."
"description": "The name of the f rule."
Copy link
Member

Choose a reason for hiding this comment

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

f -> "firewall"

@jaredmoo
Copy link
Contributor Author

Fixed, thanks. Node build seems to be hitting a transient error.

@anuchandy
Copy link
Member

@jaredmoo thanks, restarted job and now it is passing.

@jaredmoo
Copy link
Contributor Author

Can I get a review and merge here?

- Removed 'information about' wording
- Fixed 'an data warehouse'
- Made tense consistent
- Corrected TDE description
@anuchandy
Copy link
Member

@jaredmoo thanks, merging.

@AutorestCI
Copy link

@AutorestCI
Copy link

No modification for NodeJS

@AutorestCI
Copy link

@jaredmoo
Copy link
Contributor Author

Thanks!

@jaredmoo jaredmoo deleted the slo-docs branch March 1, 2017 19:44
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.

5 participants