Noor Hashem
09/16/2022, 2:58 PMid
but the provider does not provide one. Why is pact able to label this as compatible?Noor Hashem
09/16/2022, 3:16 PMBoris
09/20/2022, 12:43 AMBoris
09/20/2022, 12:44 AMNoor Hashem
09/20/2022, 12:46 AMBoris
09/20/2022, 12:47 AMNoor Hashem
09/20/2022, 12:47 AMCandy Goodison
09/20/2022, 2:09 AMNoor Hashem
09/20/2022, 3:13 AMapplication/vnd.api+json
but in the example here they have it set as application/json
. I tried changing it and I can see that now it seems to work but the issue with this is that all of our openapi files are using application/vnd.api+json
. There are hundreds of places where the application/vnd.api+json
is used and would be very difficult to replace it. Is there any other way to allow pactflow to be able to read this content format?Candy Goodison
09/20/2022, 3:52 AMapplication/vnd.api+json
? I believe in theory that should work with this content type, so this seems to point to an issue with comparison code. I can't think of another work around but will look into it moreCandy Goodison
09/20/2022, 4:15 AMapplication/vnd.api+json
, where the pact file is expecting the response to have that type, and the OAS dictates that it can produce that type. I'm not sure if this is the same use case that you are working on?
pact
{
"consumer": {
"name": "default-consumer-name"
},
"interactions": [
{
"description": "interaction description",
"request": {
"method": "post",
"path": "/does/exist"
},
"response": {
"status": 200,
"headers": {
"Content-Type": "application/vnd.api+json"
}
}
}
],
"metadata": {
"pactSpecification": {
"version": "1.0.0"
}
},
"provider": {
"name": "default-provider-name"
}
}
OAS
{
"info": {
"title": "default-title",
"version": "1.0.0"
},
"paths": {
"/does/exist": {
"post": {
"responses": {
"200": {
"description": "default-response"
}
},
"produces": [
"application/vnd.api+json"
]
}
}
},
"swagger": "2.0"
}
Candy Goodison
09/20/2022, 4:26 AMCandy Goodison
09/20/2022, 4:27 AMYousaf Nabi (pactflow.io)
Noor Hashem
09/20/2022, 2:39 PMYousaf Nabi (pactflow.io)