-
Notifications
You must be signed in to change notification settings - Fork 54
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
OAV not reporting example position for INVALID_TYPE error in request #423
Comments
@veronicagg here're the detail error message. It's clear to see the complained parameter name is 'service' though it doesn't have the line number of the example file. I would say won't fix.
|
@raych1 this issue is important one because it's hard for users to see where the problem is. Also OpenAPI Hub will not show a link to example error as well @vladbarosan @billytrend. |
@sergey-shandar , @raych1 correct, the hub wont be able to show a link without the source location |
Closed as the fix was merged. |
https://github.com/Azure/azure-rest-api-specs/blob/f9f5d84cf22d860a02fb3188a58863c4241a89b6/specification/adhybridhealthservice/resource-manager/Microsoft.ADHybridHealthService/stable/2014-01-01/ADHybridHealthService.json
Output contains an INVALID_TYPE error in the REQUEST and points to the spec but not the corresponding position in the example
Details:
Show inner error
Details: "Expected type object but found type array"
Spec location: specification/adhybridhealthservice/resource-manager/Microsoft.ADHybridHealthService/stable/2014-01-01/ADHybridHealthService.json#L6213
Operation ID - addsServices_update
Scenario = addsServices_update
Source= request
ErrorCode INVALID_TYPE
The text was updated successfully, but these errors were encountered: