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

Copy App Gateway Examples from 2018-01-01 to 2018-02-01 #2822

Merged
merged 10 commits into from
Apr 6, 2018
Merged

Copy App Gateway Examples from 2018-01-01 to 2018-02-01 #2822

merged 10 commits into from
Apr 6, 2018

Conversation

markjbrown
Copy link
Contributor

@markjbrown markjbrown commented Apr 5, 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

@AutorestCI
Copy link

AutorestCI commented Apr 5, 2018

Automation for azure-libraries-for-java

Nothing to generate for azure-libraries-for-java

@AutorestCI
Copy link

AutorestCI commented Apr 5, 2018

Automation for azure-sdk-for-node

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

@AutorestCI
Copy link

AutorestCI commented Apr 5, 2018

Automation for azure-sdk-for-python

Nothing to generate for azure-sdk-for-python

@AutorestCI
Copy link

AutorestCI commented Apr 5, 2018

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

@@ -40,6 +40,11 @@
"ApplicationGateways"
],
"operationId": "ApplicationGateways_Delete",
"x-ms-examples": {
"Delete ApplicationGateway": {
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: Spaces are not recommended as json keys,
consider naming this as Delete ApplicationGateway
This applies to all examples here

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Is this a new change? Every example name we have across all our specs have spaces in them.

Copy link
Contributor

Choose a reason for hiding this comment

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

Not a new change, but moving forward it would be nice :) won't block on this

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ok, thanks. I'll look at doing this in April or May version. Thanks!

@dsgouda
Copy link
Contributor

dsgouda commented Apr 5, 2018

@lmazuel Could you take a look at the build failure here

@markjbrown
Copy link
Contributor Author

@lmazuel if you can check on that soon I can make any corrections right away. Thanks.

@dsgouda
Copy link
Contributor

dsgouda commented Apr 6, 2018

Looks like an issue with AutoRest itself. @olydis will fix the CI soon.

@markjbrown
Copy link
Contributor Author

ok, understood. Am I able to submit a PR into the 2018-04-01 branch without triggering this error? I want to get these examples into that branch before its gets pushed as a new version. thanks.

@dsgouda dsgouda merged commit a6bca52 into Azure:master Apr 6, 2018
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