Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

pact-jvm-consumer-groovy generates incorrect contents in message pact file

See original GitHub issue

Version 4.0.2 of pact-jvm-consumer-groovy seems to have introduced a bug where the generated message pact file contains incorrect contents. Rather than being a JSON object, contents is a String representation of the expected JSON.

With this code:

def pactMessageBuilder = new PactMessageBuilder().with {
    serviceConsumer 'consumer'
    hasPactWith 'provider'
    expectsToReceive 'feed entry'
    withMetaData(contentType: 'application/json')
    withContent(contentType: 'application/json') {
        type 'foo'
        data {
            reference {
                id string('abc')
            }
        }
    }
}

4.0.2 generates:

{
  "consumer": {
    "name": "consumer"
  },
  "provider": {
    "name": "provider"
  },
  "messages": [
    {
      "description": "feed entry",
      "metaData": {
        "contentType": "application/json"
      },
      "contents": "{\n    \"type\": \"foo\",\n    \"data\": {\n        \"reference\": {\n            \"id\": \"abc\"\n        }\n    }\n}",
      "matchingRules": {
        "body": {
          "$.data.reference.id": {
            "matchers": [
              {
                "match": "type"
              }
            ],
            "combine": "AND"
          }
        }
      }
    }
  ],
  "metadata": {
    "pactSpecification": {
      "version": "3.0.0"
    },
    "pact-jvm": {
      "version": "4.0.2"
    }
  }
}

whereas 4.0.1 generates:

{
  "consumer": {
    "name": "consumer"
  },
  "provider": {
    "name": "provider"
  },
  "messages": [
    {
      "description": "feed entry",
      "metaData": {
        "contentType": "application/json"
      },
      "contents": {
        "type": "foo",
        "data": {
          "reference": {
            "id": "abc"
          }
        }
      },
      "matchingRules": {
        "body": {
          "$.data.reference.id": {
            "matchers": [
              {
                "match": "type"
              }
            ],
            "combine": "AND"
          }
        }
      }
    }
  ],
  "metadata": {
    "pactSpecification": {
      "version": "3.0.0"
    },
    "pact-jvm": {
      "version": "4.0.1"
    }
  }
}

I have created a repo to reproduce the issue here: https://github.com/qmg-rbass/pact-bug