Skip to content

Conversation

@quintinb
Copy link
Contributor

@quintinb quintinb commented Oct 9, 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

  • [ x ] The title of the PR is clear and informative.
  • [ x ] 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.
  • [ x ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
  • [ x ] If applicable, the PR references the bug/issue that it fixes.
  • [ x ] 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 Oct 9, 2018

Automation for azure-sdk-for-python

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

@AutorestCI
Copy link

AutorestCI commented Oct 9, 2018

Automation for azure-sdk-for-js

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

@AutorestCI
Copy link

AutorestCI commented Oct 9, 2018

Automation for azure-sdk-for-ruby

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-ruby#1734

@AutorestCI
Copy link

AutorestCI commented Oct 9, 2018

Automation for azure-sdk-for-node

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

@AutorestCI
Copy link

AutorestCI commented Oct 9, 2018

Automation for azure-sdk-for-java

Nothing to generate for azure-sdk-for-java

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

}
}
},
"JobError": {
Copy link
Contributor

Choose a reason for hiding this comment

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

Will it be possible to prefix "Media" to such types (JobError, JobErrorDetail, JobOutput, etc.). Since autorest didn't fully support associating separate namespaces for each swagger in this set, all of these types will be under Microsoft.Azure.EventGrid.Models namespace, and hence having the Media prefix for your types will make it more easily discoverable and avoid confusion/conflicts.

"$ref": "#/definitions/JobOutput",
"description": "Gets the output."
},
"jobCorrelationData": {
Copy link
Contributor

Choose a reason for hiding this comment

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

Minor Nit: In MediaJobStateChangeEventData, a similar property is named "correlationData" while here it is "jobCorrelationData". Is this by design, or should these names be made consistent?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is intentional because this is in the JobOutputStateChange related messages. The correlation data is a property of the Job object and not the JobOutput object (the Job contains the JobOutputs).

Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks, that sounds good.

@hovsepm
Copy link
Contributor

hovsepm commented Oct 9, 2018

@quintinb please ping me directly when all the reviewers will sign of on the PR.

Copy link
Contributor

@kalyanaj kalyanaj left a comment

Choose a reason for hiding this comment

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

I have added a couple of comments, the main one being the typenames.

Copy link
Contributor

@kalyanaj kalyanaj left a comment

Choose a reason for hiding this comment

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

Thanks @quintinb for the changes. Will it be possible to add the Media prefix for the enum type (all instances of JobState, JobErrorCode, JobErrorCategory and JobRetry) names as well?

Copy link
Contributor

@kalyanaj kalyanaj left a comment

Choose a reason for hiding this comment

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

Thanks @quintinb for the changes, the changes look good, I have added one additional comment/request regarding the names of the enum types as well, can you please consider that as well?

@hovsepm
Copy link
Contributor

hovsepm commented Oct 15, 2018

@quintinb could you take a look to @kalyanaj comment?

@quintinb
Copy link
Contributor Author

Yes, I will look at adding the Media prefix to the enum names as well.

@AutorestCI
Copy link

AutorestCI commented Oct 16, 2018

Automation for azure-sdk-for-go

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

Copy link
Contributor

@kalyanaj kalyanaj left a comment

Choose a reason for hiding this comment

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

LGTM.

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