Update to a matcher doesn't update in the contract

[surpher]

🌎 Environment

• Xcode: 11.5
• Platform: iOS
• Version/Release: master branch
• Dependency manager: Carthage 0.38

💬 Description

When writing a pact test and describing a value in body using an updated matcher, the change to that matcher is not reflected in the pact file.
If the pact file is deleted before running updated again, then the update is reflected in the pact file.

🦶 Reproduction Steps

1. Setup a pact test environment
2. Write a pact test where .willRespondWith(body:) contains a matcher:

.willRespondWith(body: [
  "related": EachLike("https://someurl.com/entity/related", min: 0, max: 5)
]

3. Run this cmd + U
4. Inspect test file to contain "matchingRules" object for:

...
"body": {
  "$.related": {
    "combine": "AND",
    "matchers": [
       {
           "match": "type",
           "max": 5,
           "min": 0
        }
    ]
  },
...

5. Update matcher to be EachLike("https://someurl.com/entity/related", min: 1, max: 10)
6. Run this cmd + U
7. Inspect test file and observe the min: and max: for the provided matcher

🤔 Expected Results

When changing the matcher, the changes should be reflected in the subsequent test runs, eg:

...
"body": {
  "$.related": {
    "combine": "AND",
    "matchers": [
       {
           "match": "type",
           "max": 10,
           "min": 1 
        }
    ]
  },
...

😲 Actual Results

The changes to min: and max: are not recorded and remain set to max: 5 and min: 0

⑂ Possible workaround(s)

Before running the tests again with the changes to any of the matchers (tested with changing a SomethingLike() to EqualTo()), remove any existing pact files in order to completely re-generate any and all pact files.

[surpher]

The code that is writing the file is the Pact Mock Server which is brought in as an external dependency (Pact Mock Server). Already reached out to pinpoint where the issue occurs.

An option would be to either forcefully clean any existing JSON files in the target folder before verifying any of the interactions;
Or maybe provide an optional flag to clean up the folder before running the tests.

[surpher]

This might not be a bug but expected behaviour. If it is confirmed that it is working as expected, documentation will be updated accordingly and/or an alternative handling of this will be looked into in PactSwift.

[surpher]

Confirmed it is a bug in pact_mock_server (pact-foundation/pact-reference#77).
Bug should be fixed with your next build when git submodule update --init --recursive pulls the fixes done in pact-reference submodule.