fix(Visual Recognition V3): Fixed example to not send null _classifierID. Revised service to send a proper filename #523
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…rID. Revised service to send a
mamoonraja
approved these changes
Feb 26, 2019
|
🎉 This PR is included in version 2.15.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This pull request addresses an issue where the VisualRecognition example was classifying an image using a null classifierID. This was an artifact from when the example created a classifier. This was removed because the service would sometimes make "ghost classifiers" that could not be removed by the user.
Additionally the request was revised to send a proper filename. Previously it was sending the content type as the filename.
Fixes #522