JSON::ParserError when response body contains a JSON primitive

I’m working on consumer and provider tests with PactNet, but have consistently run into ParserErrors when the response/request bodies contain primitives. As an example:

{
      "description": "A GET request to retrieve a user's ID",
      "providerState": "A user that exists in the System",
      "request": {
        "method": "get",
        "path": "/api/users",
        "query": "username=bill",
      },
      "response": {
        "status": 200,
        "headers": {
          "Content-Type": "application/json; charset=utf-8"
        },
        "body": "c43665eb-b9c8-4787-94b6-e19bd65c9225",
        "matchingRules": {
          "$.body": {
            "match": "type"
          }
        }
      }
    }

It was claimed in issue #139 (before it was closed) that strings alone are not valid JSON, but as of at least Dec 2017 this is untrue. So it would be nice if this discrepancy could get resolved, or at least if some piece of documentation could clarify which JSON spec Pact expects services to follow. Thanks.

[neilcampbell]

This will be available in PactNet 2.5.3, which is building as we speak.

[bethesque]

My bad, 1.82.3. Travis has just taken a really long time to kick off the build.