-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Add areaOfInterest and detectObject to CV API #4771
Conversation
* Replace the current swagger with an auto-generated one. * Add example files for areaOfInterest and detectObject. * Fix example validation errors for analyze and describe. * A few fixes for generating java sdk
If you're a MSFT employee, click this link |
Can one of the admins verify this patch? |
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-rubyThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-javaThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-nodeThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-goA PR has been created for you: |
Automation for azure-sdk-for-jsThe initial PR has been merged into your service PR: |
Hi @mirzamo, earlier today I had a meeting with Hui and Cha today. |
specification/cognitiveservices/data-plane/ComputerVision/stable/v2.0/ComputerVision.json
Outdated
Show resolved
Hide resolved
specification/cognitiveservices/data-plane/ComputerVision/stable/v2.0/ComputerVision.json
Outdated
Show resolved
Hide resolved
specification/cognitiveservices/data-plane/ComputerVision/stable/v2.0/ComputerVision.json
Outdated
Show resolved
Hide resolved
"InvalidModel", | ||
"CancelledRequest", | ||
"NotSupportedVisualFeature", | ||
"FailedToProcess", |
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 seems to be a breaking change for your API - current SDKs will not be able to handle these new enums. Only enums with "modelAsString" set to true are allowed to add new enum values.
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.
Can you help clarify? If the service returns one of these new values in the JSON, aren't current clients screwed anyway?
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.
@jianghaolu Any comments?
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.
Yes That's what I mean by saying the rest API is going to break the clients.
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.
aren't current clients screwed anyway
This doesn't justify breaking the clients after breaking the APIs. If this list is supposed to grow you should mark "modelAsString" to true in this PR. This PR is bringing breaking changes anyways (unfortunately) but there will be no more in the future.
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 changed it to true to prevent future breaking changes. Also in here.
@yangyuan I addressed all of your comments. |
@mirzamo |
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.
Look good from my side.
Also passes typo check.
"metadata": { | ||
"width": 100, | ||
"height": 100, | ||
"format": "Jpeg" |
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 an idea, wouldn't jpeg
or JPEG
be better?
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 agree, but for all the of other services it's Jpeg
and I think it's better to keep them 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.
Just curious, what services you are referring to? I searched before and didn't find anyother..
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.
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.
Oh you mean other operations
, I thought you mean other services
specification/cognitiveservices/data-plane/ComputerVision/stable/v2.0/ComputerVision.json
Outdated
Show resolved
Hide resolved
specification/cognitiveservices/data-plane/ComputerVision/stable/v2.0/ComputerVision.json
Outdated
Show resolved
Hide resolved
… ComputerVisonErrors enum
* Add areaOfInterest and detectObject * Replace the current swagger with an auto-generated one. * Add example files for areaOfInterest and detectObject. * Fix example validation errors for analyze and describe. * A few fixes for generating java sdk * Addressing commets: reorder some keys * fix formatting * Changing modelAsString parameter to ture to be able to add new values ComputerVisonErrors enum
This PR has been approved in the private repo. As we are about to release these features to public, I'm sending this PR.
https://github.com/Azure/azure-rest-api-specs-pr/pull/607
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.