Hi, probably this is a common question, I have the...
# generalm
Moises Siles
06/27/2023, 12:01 AMHi, probably this is a common question, I have the following test
Copy code
const reports = await getReportByID("xxxxxxxxxxx");
return expect(reports).to.deep.equal(getReportBodyExpectation) Copy code
1.1) has a matching body
$ -> Type mismatch: Expected List [{"account":{.........
but received Map {"account":{"accob
Boris
06/27/2023, 12:13 AMIt's valid to use any JSON type as the root of a document, but objects give the greatest flexibility.
If your endpoint represents a singular resource (not a list) then removing the list wrapper should be fine. But if it genuinely represents a list of resources, you should consider wrapping it in another object, and giving the list a field name.
✅ 1
m
Matt (pactflow.io / pact-js / pact-go)
06/27/2023, 3:02 AM
Yep, the issue is that your consumer test is expecting an array, but your provider is returning an object
☝️ 1
Matt (pactflow.io / pact-js / pact-go)
06/27/2023, 3:04 AM
You need to update your test to expect the correct shape the provider actually returns (an object) or modify the API provider to actually return an object of the shape you expect (presumably by working with that team to arrange the modification)
Matt (pactflow.io / pact-js / pact-go)
06/27/2023, 3:05 AM
the easy fix is removing the [ ] from my json files, but is there a nice way or something that I should take a lookin case it’s not clear, you never should be modifying the JSON files directly. They represent what your API client is doing (in this case, expecting an array). By removing it from the pact file, you are modifying what the contract captures and potentially deviating from reality - this is likely to result in breakages
👍 1
2 Views