Feat/composing matching rules

[rholshausen]

Implements #399

TLDR - This allows an array to be specified with the pact:matcher:type attribute to be able to have multiple matching rules.

For example, you could do something like (just making this up, may not be valid):

{
    "pact:matcher:type": [
        { "pact:matcher:type": "regex", "regex": "\\w{3}-\\d+" },
        { "pact:matcher:type": "include", "value": "XYZ" }
    ]
}

[rholshausen]

As I was in that space, I also added support for the matching rule definition expressions. So you can also do

{
    "pact:matcher:type": "eachKey(matching(regex, '\\w{3}-\\d+', 'AUK-155332')), eachValue(matching(type, ''))",
}

Just note that using references (matching($'Example')) will not work.

[JP-Ellis]

Looks all pretty sensible to me.

Should the compatibility suite also be updated to make sure downstream libraries consistently use these?

[rholshausen]

Looks all pretty sensible to me.

Should the compatibility suite also be updated to make sure downstream libraries consistently use these?

This is more an implementation detail. The language implementations can choose to use this form or use the FFI functions directly. The compatibility suite should assert the behavior, regardless.

[mefellows]

Looks all pretty sensible to me.
Should the compatibility suite also be updated to make sure downstream libraries consistently use these?

This is more an implementation detail. The language implementations can choose to use this form or use the FFI functions directly. The compatibility suite should assert the behavior, regardless.

Yeah it was more the point of being able to add multiple matchers to a single field.

Ditto expressions.

This looks good though!