MatchersV3.string() with no arguments doesn't match strings

[TimothyJones]

Software versions

• Consumer Pact library: 10.1.3

Issue Checklist

Please confirm the following:

• I have upgraded to the latest
• I have the read the FAQs in the Readme
• I have triple checked, that there are no unhandled promises in my code and have read the section on intermittent test failures
• I have set my log level to debug and attached a log file showing the complete request/response cycle
• For bonus points and virtual high fives, I have created a reproduceable git repository (see below) to illustrate the problem

Expected behaviour

MatchersV3.string() should match any string

Actual behaviour

this line has no default argument, so MatchersV3.string() actually produces { 'pact:matcher:type': 'type', value: undefined } which will not work as expected.

Steps to reproduce

Make a pact expectation that includes MatchersV3.string()

Relevant log files

N/A

[TimothyJones]

This is kind of a breaking change, since the V2 matcher does have a default argument.