Tatiana Shepeleva
05/15/2023, 5:51 AMMatt (pactflow.io / pact-js / pact-go)
Matt (pactflow.io / pact-js / pact-go)
Matt (pactflow.io / pact-js / pact-go)
Tatiana Shepeleva
05/15/2023, 6:47 AMResponse Body Contains Unknown Information
No schema found for response body
Mismatched Pact Path:
[root].interactions[0].response.body
Mismatched Provider Path:
[root].paths./api/v1/variables.get.responses.200
It feels like the validator stoped recognising out schemas or something. Let me have a look at the link you’ve sharedVoon Siong Wong
05/15/2023, 6:56 AMMatt (pactflow.io / pact-js / pact-go)
I suspect you were a subset of our customers who did not have the correct content types set, and as such, were getting a false sense of security. The previous behaviour was to skip such checks, which is antithetical to the objective hereCopy codeNo schema found for response body
Tatiana Shepeleva
05/15/2023, 7:09 AMMatt (pactflow.io / pact-js / pact-go)
Matt (pactflow.io / pact-js / pact-go)
Matt (pactflow.io / pact-js / pact-go)
Tatiana Shepeleva
05/15/2023, 9:48 AMaccept
header "accept": "application/json, text/plain, */*"
in the consumer contract. Changing it to "accept": "application/json"
helped.
Thanks for your help!Voon Siong Wong
05/15/2023, 11:51 AMaccept
. I'll add that to our backlogMatt (pactflow.io / pact-js / pact-go)
Matt (pactflow.io / pact-js / pact-go)