Skip to content
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

Added/Updating Logic Apps Management Client endpoints #2727

Closed

Conversation

refortie
Copy link
Contributor

@refortie refortie commented Mar 21, 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

@refortie refortie requested a review from a user March 21, 2018 22:47
@refortie refortie requested a review from tiffanyachen as a code owner March 21, 2018 22:47
@daviburg
Copy link
Member

Reid, are you able to add Logic App engineers as reviewers for this PR? We should get all the authors of the operations you are adding coverage for to review their piece.

@refortie
Copy link
Contributor Author

@daviburg

Reid, are you able to add Logic App engineers as reviewers for this PR? We should get all the authors of the operations you are adding coverage for to review their piece.

I'm not super familiar with github's ui, I'll see if I can figure out how to add them

"properties": {
"value": {
"description": "Collection of resources",

Copy link
Member

Choose a reason for hiding this comment

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

impersonate a user account

Doesn't have to be the author's user account.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed

"properties": {
"value": {
"description": "Collection of resources",

Copy link
Member

Choose a reason for hiding this comment

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

should oauthSettings be two words and capitalized for English language instead of the programming language Camel casing of a variable name?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Since oathSettings isn't a property contained within this document. I think it better to use the English version of it.

"type": "string"
},
"etag": {
"description": "Resource etag",
Copy link
Member

Choose a reason for hiding this comment

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

Check if the casing should be ETag as it is an acronym.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I believe so

},
"filterParameter": {
"name": "$filter",
"description": "The filter to apply on the operation.",
Copy link
Member

Choose a reason for hiding this comment

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

most sentences in this do not end with a dot so likely neither should this one.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed

"exportParameter": {
"type": "string",
"name": "export",
"description": "flag showing whether to export API definition in format specified by Accept header",
Copy link
Member

Choose a reason for hiding this comment

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

Capitalize "Flag"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed

"parameters": {
"locationParameter": {
"name": "location",
"description": "The location.",
Copy link
Member

Choose a reason for hiding this comment

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

consistent ending of lines with or without dot

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Made consistent all over by removing them

"tags": [
"Connections"
],
"summary": "Update an existing connection",
Copy link
Member

Choose a reason for hiding this comment

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

should all operations have a summary like this one? delete below doesn't

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, they all should. Will doublecheck all of them

],
"summary": "Update an existing connection",
"operationId": "Connections_Update",
"description": "Update a connection",
Copy link
Member

Choose a reason for hiding this comment

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

Verb is with present tense below, i.e. Deletes
Should this here be Updates then?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Changed

"tags": [
"Custom APIs"
],
"summary": "Moves the Custom API",
Copy link
Member

Choose a reason for hiding this comment

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

consistent capitalization for custom in custom API

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed

],
"summary": "Gets a specific gateway",
"operationId": "ConnectionGateways_Get",
"description": "Gets a specific gateway for under a subscription and in a specific resource group",
Copy link
Member

Choose a reason for hiding this comment

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

"for under" is that proper English? above was just "under"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Nope, that is not proper English. Fixed

@refortie
Copy link
Contributor Author

Need the examples files. Going to close this till those are done

@refortie refortie closed this Mar 22, 2018
@AutorestCI
Copy link

AutorestCI commented Mar 22, 2018

Automation for azure-sdk-for-node

Encountered a Subprocess error: (azure-sdk-for-node)

Command: ['/usr/local/bin/autorest', '/tmp/tmpdie3d2x7/rest/specification/web/resource-manager/readme.md', '--license-header=MICROSOFT_MIT_NO_VERSION', '--node-sdks-folder=/tmp/tmpdie3d2x7/sdk', '--nodejs']
Finished with return code -9
and output:

AutoRest code generation utility [version: 2.0.4259; node: v7.10.1]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
   Loading AutoRest core      '/tmp/.autorest/@microsoft.azure_autorest-core@2.0.4259/node_modules/@microsoft.azure/autorest-core/dist' (2.0.4259)
   Loading AutoRest extension '@microsoft.azure/autorest.nodejs' (~2.1.25->2.1.32)
   Loading AutoRest extension '@microsoft.azure/autorest.modeler' (2.3.44->2.3.44)
Shutting Down

@AutorestCI
Copy link

AutorestCI commented Mar 22, 2018

Automation for azure-libraries-for-java

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-libraries-for-java#327

@AutorestCI
Copy link

AutorestCI commented Mar 22, 2018

Automation for azure-sdk-for-python

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-python#2065

@AutorestCI
Copy link

AutorestCI commented Mar 22, 2018

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

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.

4 participants