-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Update the MediaServices.json file in the EventGrid DataPlane SDK #4111
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
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-jsThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-rubyA 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: |
Automation for azure-sdk-for-nodeThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-javaNothing to generate for azure-sdk-for-java |
|
Can one of the admins verify this patch? |
| } | ||
| } | ||
| }, | ||
| "JobError": { |
There was a problem hiding this comment.
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": { |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, that sounds good.
|
@quintinb please ping me directly when all the reviewers will sign of on the PR. |
kalyanaj
left a comment
There was a problem hiding this 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.
kalyanaj
left a comment
There was a problem hiding this 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?
kalyanaj
left a comment
There was a problem hiding this 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?
|
Yes, I will look at adding the Media prefix to the enum names as well. |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
kalyanaj
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
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