Pact-jvm: Path regex matchers are creating an empty entry in the pact file

Created on 30 Jul 2018 · 4Comments · Source: pact-foundation/pact-jvm

We're trying to use the generated pacts from pact-jvm-consumer-groovy using pact-foundation/pact-stub-server.

The problem is that the generated pact will add and empty string "" in the matching rules for path, which seems incorrect per V3 specification. In the pact-stub-server, the request won't match

 "matchingRules": {
    "body": {
    },
    "header": {
      "Authorization": {
        "matchers": [
          {
            "match": "regex",
            "regex": "Bearer .*"
          }
        ],
        "combine": "AND"
      },
      "X-Correlation-id": {
        "matchers": [
          {
            "match": "regex",
            "regex": "[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}"
          }
        ],
        "combine": "AND"
      }
    },
    "path": {
      "": {
        "matchers": [
          {
            "match": "regex",
            "regex": "/order/[^/.]+/shipping"
          }
        ],
        "combine": "AND"
      }
    }
  }

If we change path to:

    "path": {
        "matchers": [
          {
            "match": "regex",
            "regex": "/order/[^/.]+/shipping"
          }
        ],
        "combine": "AND"
      }
  }

It will work. We checked the code and it looks like it will be always adding an empty entry when recording the expectation, independently of the jvm-consumer

Created the issue here as it seems more relevant to how all jvm-consumers are writing the pact file.

bug

Source