Closed leonwanghui closed 5 years ago
When working on #666, we saw errors validating the Swagger too:
Validating spec (/local/swagger.yaml)
Errors:
-attribute paths.'/v2/service_instances/{instance_id}'. Declared path parameter instance_id needs to be defined as a path parameter in path or operation level
-attribute paths.'/v2/service_instances/{instance_id}/service_bindings/{binding_id}/last_operation'. Declared path parameter instance_id needs to be defined as a path parameter in path or operation level
-attribute paths.'/v2/service_instances/{instance_id}/service_bindings/{binding_id}'. Declared path parameter binding_id needs to be defined as a path parameter in path or operation level
-attribute paths.'/v2/service_instances/{instance_id}/last_operation'. Declared path parameter instance_id needs to be defined as a path parameter in path or operation level
-attribute paths.'/v2/service_instances/{instance_id}/service_bindings/{binding_id}/last_operation'. Declared path parameter binding_id needs to be defined as a path parameter in path or operation level
-attribute paths.'/v2/service_instances/{instance_id}/service_bindings/{binding_id}'. Declared path parameter instance_id needs to be defined as a path parameter in path or operation level
[error] Spec has 6 errors.
@blgm I noticed that, but when I use go-swagger tool to validate swagger.yaml and it shows no errors, which is odd.
I guess the validation tools have slight implementation differences.
It would be a step forward to validating using a tool in the CI. If we find that we prefer other tools, or want to validate using more than one tool, we can do that in the future.
What is the problem? Recently I found an openapi validation tool from OpenAPITools code repo, and when I try to validate the openapi.yaml, some errors are reported below:
Who does this affect? None
Do you have any proposed solutions? Fix all errors reported above.
Additional context Add any other context or screenshots can go here.