Bas Dijkstra
05/10/2024, 8:30 AMUnable to parse "oas": Swagger schema validation failed. #/paths/~1api~1v1~1LogVariables/get/parameters/2 must have required property 'schema' #/paths/~1api~1v1~1LogVariables/get/parameters/2 must have required property 'content' #/paths/~1api~1v1~1LogVariables/get/parameters/2 must match exactly one schema in oneOf #/paths/~1api~1v1~1LogVariables/get/parameters/2 must have required property '$ref' #/paths/~1api~1v1~1LogVariables/get/parameters/2 must match exactly one schema in oneOf #/paths/~1api~1v1~1Request/post/parameters/0 must have required property 'schema' #/paths/~1api~1v1~1Request/post/parameters/0 must have required property 'content' #/paths/~1api~1v1~1Request/post/parameters/0 must match exactly one schema in oneOf #/paths/~1api~1v1~1Request/post/parameters/0 must have required property '$ref' #/paths/~1api~1v1~1Request/post/parameters/0 must match exactly one schema in oneOf #/paths/~1api~1v1~1underwriting~1Request/post/parameters/0 must have required property 'schema' #/paths/~1api~1v1~1underwriting~1Request/post/parameters/0 must have required property 'content' #/paths/~1api~1v1~1underwriting~1Request/post/parameters/0 must match exactly one schema in oneOf #/paths/~1api~1v1~1underwriting~1Request/post/parameters/0 must have required property '$ref' #/paths/~1api~1v1~1underwriting~1Request/post/parameters/0 must match exactly one schema in oneOf #/paths/~1api~1v1~1underwriting~1check~1{sessionId}/get/parameters/1 must have required property 'schema' #/paths/~1api~1v1~1underwriting~1check~1{sessionId}/get/parameters/1 must have required property 'content' #/paths/~1api~1v1~1underwriting~1check~1{sessionId}/get/parameters/1 must match exactly one schema in oneOf #/paths/~1api~1v1~1underwriting~1check~1{sessionId}/get/parameters/1 must have required property '$ref' #/paths/~1api~1v1~1underwriting~1check~1{sessionId}/get/parameters/1 must match exactly one schema in oneOf #/paths/~1api~1v1~1underwriting~1check/post/parameters/0 must have required property 'schema' #/paths/~1api~1v1~1underwriting~1check/post/parameters/0 must have required property 'content' #/paths/~1api~1v1~1underwriting~1check/post/parameters/0 must match exactly one schema in oneOf #/paths/~1api~1v1~1underwriting~1check/post/parameters/0 must have required property '$ref' #/paths/~1api~1v1~1underwriting~1check/post/parameters/0 must match exactly one schema in oneOf #/paths/~1api~1v1~1underwriting~1check/delete/parameters/0 must have required property 'schema' #/paths/~1api~1v1~1underwriting~1check/delete/parameters/0 must have required property 'content' #/paths/~1api~1v1~1underwriting~1check/delete/parameters/0 must match exactly one schema in oneOf #/paths/~1api~1v1~1underwriting~1check/delete/parameters/0 must have required property '$ref' #/paths/~1api~1v1~1underwriting~1check/delete/parameters/0 must match exactly one schema in oneOf #/paths/~1api~1v2~1underwriting~1sync/post/parameters/0 must have required property 'schema' #/paths/~1api~1v2~1underwriting~1sync/post/parameters/0 must have required property 'content' #/paths/~1api~1v2~1underwriting~1sync/post/parameters/0 must match exactly one schema in oneOf #/paths/~1api~1v2~1underwriting~1sync/post/parameters/0 must have required property '$ref' #/paths/~1api~1v2~1underwriting~1sync/post/parameters/0 must match exactly one schema in oneOf #/paths/~1api~1v2~1underwriting~1async/post/parameters/0 must have required property 'schema' #/paths/~1api~1v2~1underwriting~1async/post/parameters/0 must have required property 'content' #/paths/~1api~1v2~1underwriting~1async/post/parameters/0 must match exactly one schema in oneOf #/paths/~1api~1v2~1underwriting~1async/post/parameters/0 must have required property '$ref' #/paths/~1api~1v2~1underwriting~1async/post/parameters/0 must match exactly one schema in oneOf
I interpret this as 'the schema itself is invalid, and therefore I can't match it with a consumer contract'. Is that true and if so, what can I do to resolve it?Matt (pactflow.io / pact-js / pact-go)
Matt (pactflow.io / pact-js / pact-go)
tenant parameter doesn’t have a data type / schema associated with it:
Structural error at paths./api/v1/Request.post.parameters.0
should have either aorschemapropertycontent
Matt (pactflow.io / pact-js / pact-go)
- name: tenant
in: header
description: Tenant id
required: true
Good:
- name: tenant
in: header
schema:
type: string
description: Tenant id
required: true
That’s most of the errors sorted, as it’s a repeated problemMatt (pactflow.io / pact-js / pact-go)
CreateRawRequestAsync so one just needs renaming (I don’t think this breaks PactFlow but should be fixed anyway)Matt (pactflow.io / pact-js / pact-go)
DELETE. I don’t think this affects PactFlow either, but is a non-standard thing to doMatt (pactflow.io / pact-js / pact-go)
Bas Dijkstra
05/13/2024, 6:24 AM