Azure / Azure/azure-rest-api-specs
ComputerVision OCR using non-standard LRO protocol
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 3d 37m
- Merged PRs (30d)
- 446
Description
Cognitive Services Computer Vision OCR is currently using a non-standard LRO protocol as described [here](https://github.com/Azure/azure-rest-api-specs/pull/5314/files#diff-79de737cbafb0699b36bc938b717ec24R114). They should change their LRO implementation to adhere to the protocol explain in [this document](https://github.com/shahabhijeet/adx-documentation-pr/blob/docLro/sdks/LRO/LRO_AzureSDK.md).
Contributor guide
Research direction
Start by reviewing the referenced Azure REST API specs pull request diff and the linked LRO document to compare the Computer Vision OCR behavior with the documented protocol. Done means the OCR specification reflects the standard LRO implementation described there.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, computer-vision
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100