Skip to content

Conversation

@shakao
Copy link
Contributor

@shakao shakao commented Apr 13, 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 13, 2018

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

@AutorestCI
Copy link

AutorestCI commented Apr 13, 2018

Automation for azure-sdk-for-python

Nothing to generate for azure-sdk-for-python

@AutorestCI
Copy link

AutorestCI commented Apr 13, 2018

Automation for azure-libraries-for-java

Nothing to generate for azure-libraries-for-java

@AutorestCI
Copy link

AutorestCI commented Apr 13, 2018

Automation for azure-sdk-for-node

Nothing to generate for azure-sdk-for-node

"image": "multipart-form-data",
"knowledgeRequest": {
"imageInfo": {
imageInsightsToken: "{Image Insights Token}",
Copy link
Contributor

Choose a reason for hiding this comment

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

That's not a valid JSON.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

updated

@shakao
Copy link
Contributor Author

shakao commented Apr 13, 2018

@swhite-msft The full swagger spec for the Image Visual Search API!

@swhite-msft
Copy link
Contributor

@shakao I don't think you want to merge this to master. I think you want it in the release-build-cognitive-search release branch.

@sudhansu88
Copy link
Contributor

@swhite-msft : We have checked in all Specs to master only. What branch is this " release-build-cognitive-search" ?

@sudhansu88
Copy link
Contributor

sudhansu88 commented Apr 16, 2018

All well ??
@sergey-shandar : Could you please merge ?

"in": "formData",
"description": "A JSON object containing information about the image. The image and imageInsightsToken fields are mutually exclusive – the body of the request must include only one of them.",
"required": false,
"type": "string"
Copy link
Contributor

Choose a reason for hiding this comment

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

It looks like the type has to be KnowledgeRequest instead of string.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We don't have the ability to specify objects in the body of a POST request using multipart form-data with Swagger 2.0, so it's encoded as a string for now. I've updated the example to match.

"accentColor":"956236"
},
{
"webSearchUrl":"https:\/\/www.bing.com\/images\/search?view=detailv2&FORM=OIIRPO
Copy link
Contributor

@sergey-shandar sergey-shandar Apr 16, 2018

Choose a reason for hiding this comment

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

image._type is missing.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

updated

"accentColor":"956236"
},
{
"webSearchUrl":"https:\/\/www.bing.com\/images\/search?view=detailv2&FORM=OIIRPO
Copy link
Contributor

Choose a reason for hiding this comment

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

tags[*]._type is expected, according to the swagger.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

updated

@azuresdkciprbot
Copy link

Hi There,

I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:

File: specification/cognitiveservices/data-plane/VisualSearch/readme.md
Before the PR: Warning(s): 0 Error(s): 0
After the PR: Warning(s): 0 Error(s): 0

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@sudhansu88
Copy link
Contributor

@sergey-shandar : We are waiting for your sign off. Please let us know if the spec is ready to be merged. We will update Release branch Folks to pick final signed off version of spec and merge in Release branch instead of master.

@sergey-shandar
Copy link
Contributor

@shakao
Copy link
Contributor Author

shakao commented Apr 17, 2018

@sergey-shandar the first failure is because it's expecting a type "file", and the example placeholder is a string, which i based off the existing Custom Vision API example. i don't think there's a way to include a file upload in the example json?

@azuresdkciprbot
Copy link

Hi There,

I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:

File: specification/cognitiveservices/data-plane/VisualSearch/readme.md
Before the PR: Warning(s): 0 Error(s): 0
After the PR: Warning(s): 0 Error(s): 0

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@sergey-shandar
Copy link
Contributor

@shakao yes, it's a known bug. Please ignore the first one and have a look the response.

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.

6 participants