<#CLS16AVEE|> Response Body is incompatible with t...
# pactflowv
Venkat Konda
09/11/2023, 9:14 PM#CLS16AVEE Response Body is incompatible with the response body schema in the spec file: should NOT have additional properties - PhoneAddress
Mismatched Pact path:
[root].interactions[0].response.body.UpdatedContact.ContactPoint
mismatched Provider Path:
[root].paths........................schema.properties.UpdatedContact.properties.ContactPoint.additionalProperties
My provider response object contains in this format:
Body:
{
"UpdatedContact": {
"ContactPoint":{
"PhoneAddress": {
"code":"+77",
"phoneNumber":"1234567"
}
}
}
}
My spec for the following is below attachment in a truncated format:
m
Matt (pactflow.io / pact-js / pact-go)
09/11/2023, 10:42 PM
Hi Venkat, I can already see at least 2 discrepancies:
1.
PhoneAddressPhoneAddres.codePhoneAddress.internationalCode👀 1
Matt (pactflow.io / pact-js / pact-go)
09/11/2023, 10:43 PM
One guess (you could try):
Copy code
EditCustDetailsContactPoint:
type: object # <- try commenting this out
properties:
ContactPoint:
anyOf:
- $ref: '#/components/schemas/VerifyEndpointPhoneData'
- $ref: '#/components/schemas/VerifyEndpointEmailData'🙌 1
v
Venkat Konda
09/12/2023, 8:37 AMThanks Matt,
Will sort the first comment
For EditCustDetailsContactPoint, actual type was not there but later added. let me check again.
👍 1
Venkat Konda
09/12/2023, 9:29 AMPhoneAddress.code was my typo...sorry for that.
👍 1
Venkat Konda
09/12/2023, 7:40 PM@Matt (pactflow.io / pact-js / pact-go)
I think the spec is missing this discriminator keyword as we are using anyof openAPI schema
https://docs.pactflow.io/docs/bi-directional-contract-testing/contracts/oas/keyword-support/
Venkat Konda
09/12/2023, 9:40 PMIt turned out that the discriminator is for oneOf not for anyOf.
m
Matt (pactflow.io / pact-js / pact-go)
09/13/2023, 1:37 AM
It turned out that the discriminator is for oneOf not for anyOf.correct. It’s to discriminate distinctly between 2 or more schemas.
anyOfv
Venkat Konda
09/13/2023, 10:03 AMThanks @Matt (pactflow.io / pact-js / pact-go)
Now it brings back the question "What is making the error by PactFlow"
m
Matt (pactflow.io / pact-js / pact-go)
09/13/2023, 12:02 PM
I believe it’s a known issue with the
type: objectv
Venkat Konda
09/13/2023, 12:14 PMWe removed type:object but it didn’t work.
If we remove anyOf , it is working but the provider is not going to change that.
m
Matt (pactflow.io / pact-js / pact-go)
09/13/2023, 12:16 PM
of course
Matt (pactflow.io / pact-js / pact-go)
09/13/2023, 12:29 PM
OK, i have reproduced the issue
Matt (pactflow.io / pact-js / pact-go)
09/13/2023, 12:29 PM
the good news is that that’s actually fixed in the latest version of that code
🙌 1
Matt (pactflow.io / pact-js / pact-go)
09/13/2023, 12:29 PM
the bad news is that it’s not yet released to on-prem
Matt (pactflow.io / pact-js / pact-go)
09/13/2023, 12:30 PM
the redeeming news is that it’s not too far away (probably < 1 week)
🙌 1
v
Venkat Konda
09/13/2023, 12:33 PMWonderful, thanks for your prompt attention. Atleast we know the issue and resolution.
❤️ 1
m
Matt (pactflow.io / pact-js / pact-go)
09/13/2023, 12:34 PM
No worries. I’ll respond to your email ticket now also