-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Issues resource with Comments and Attachments subresources were added #2576
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
|
@ravbhatnagar new operations |
Automation for azure-sdk-for-pythonNothing to generate for azure-sdk-for-python |
6baa209 to
f164fc7
Compare
Automation for azure-sdk-for-goEncountered a Subprocess error: (azure-sdk-for-go)
Command: ['/usr/local/bin/autorest', '/tmp/tmpm5vf3ydx/rest/specification/apimanagement/resource-manager/readme.md', '--go', '--go-sdk-folder=/tmp/tmpm5vf3ydx/sdk', '--multiapi', '[email protected]/autorest.go@~2.1.95', '--use-onever', '--verbose'] 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/@[email protected]/node_modules/@microsoft.azure/autorest-core/dist' (2.0.4259)
Loading AutoRest extension '@microsoft.azure/autorest.go' (~2.1.95->2.1.95)
Loading AutoRest extension '@microsoft.azure/autorest.modeler' (2.3.38->2.3.38)
Processing batch task - {"tag":"package-2017-03"} .
Processing batch task - {"tag":"package-2016-10"} .
Processing batch task - {"tag":"package-2016-07"} .
FATAL: swagger-document/compose - FAILED
FATAL: Error: '$.parameters.SubscriptionIdParameter.description' has incompatible values (---
-
Subscription credentials which uniquely identify Microsoft Azure subscription.
The subscription ID forms part of the URI for every service call.
, ---
-
Subscription credentials which uniquely identify the Microsoft Azure
subscription. The subscription ID forms part of the URI for every service
call.
).
Process() cancelled due to exception : '$.parameters.SubscriptionIdParameter.description' has incompatible values (---
-
Subscription credentials which uniquely identify Microsoft Azure subscription.
The subscription ID forms part of the URI for every service call.
, ---
-
Subscription credentials which uniquely identify the Microsoft Azure
subscription. The subscription ID forms part of the URI for every service
call.
).
Failure during batch task - {"tag":"package-2016-07"} -- Error: '$.parameters.SubscriptionIdParameter.description' has incompatible values (---
-
Subscription credentials which uniquely identify Microsoft Azure subscription.
The subscription ID forms part of the URI for every service call.
, ---
-
Subscription credentials which uniquely identify the Microsoft Azure
subscription. The subscription ID forms part of the URI for every service
call.
)..
Error: '$.parameters.SubscriptionIdParameter.description' has incompatible values (---
-
Subscription credentials which uniquely identify Microsoft Azure subscription.
The subscription ID forms part of the URI for every service call.
, ---
-
Subscription credentials which uniquely identify the Microsoft Azure
subscription. The subscription ID forms part of the URI for every service
call.
). |
5d9e129 to
0950562
Compare
… under API resource
0950562 to
bf2a1ed
Compare
…into glfeokti_issues_resource
|
Hi, @ravbhatnagar! Could you please take a look? Thanks! |
|
Looks good. Signing off from ARM side. |
|
@olydis Don't merge this PR, as the API is not out yet. |
olydis
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.
Looking good overall, just one likely bug and some minor suggestions! 🙂 On which date is this API going live?
| "in": "body", | ||
| "required": true, | ||
| "schema": { | ||
| "$ref": "#/definitions/IssueAttachmentPutContract" |
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.
Just a non-technical suggestion: I'd not put "Put" in the name of this class, it's a technical detail of the API and not helpful to SDK users. Unfortunately, I thing there is no big consensus for naming these things, but I've seen things like "...Setting" or "...Parameters" before (where "..." is the underlying resource type, i.e. IssueAttachmentContract in this case). Maybe you can take a quick look at other "put" operations in this RP to find the common naming strategy 🙂
| ], | ||
| "description": "Issue contract Properties." | ||
| }, | ||
| "IssueCommentCollection": { |
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.
Applies to all ...Collection types: Could you mark all properties as readOnly: true?
| ], | ||
| "description": "Issue Attachment Contract details." | ||
| }, | ||
| "IssueAttachmentPutContractProperties": { |
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.
not used anywhere - thanks to the example you provided for the put operation, this was caught by our tooling 😃 Pretty sure you wanted to use this schema for IssueAttachmentPutContract's properties. (My naming comment regarding using "Put" in the name of this type of course also applies for this type)
|
@promoisha please respond to outstanding comments/questions. Will otherwise close this PR due to inactivity (can be reopened once you are ready to move forward). |
|
@salameer @promoisha Closing due to inactivity. Feel free to reopen once you're ready to address outstanding issues. |
Automation for azure-libraries-for-javaNothing to generate for azure-libraries-for-java |
Automation for azure-sdk-for-nodeThe initial PR has been merged into your service PR: |
|
@promoisha Is this API already public/live or when is that going to happen? Just so I can merge at the right point in time 🙂 |
olydis
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! Will merge once you confirmed whether/when this is live 🙂
|
@olydis it's hitting the production right now, so I assume it's safe to merge :). Thanks a lot! |
|
@promoisha Thank you! |
Issues resource with Comments and Attachments subresources were added under theAPI resource.
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