#662 [V3] eachKeyLike doesn't ignore the key's value when matching Issue created by francislobo Software versions • OS: Win 10 • Consumer Pact library: "@pact_foundation/pact": "10.0.0-beta.34", "jest-pact": "0.9.0-beta.v3", • Provider Pact library: pact-jvm-provider-gradle', version: '4.0.10' • Node Version: v12.13.1 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 ☐ 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 For an example data shown here, the PACT generated using PACT JVM and PACT JS are different. Specifically this sectiongenerated from the eachkeylike matchers. This breaks the eachkeylike matcher where the actual key should be ignored and only the value (contents) of the key must be matched. Pact generated from JS Pact generated from JVM NOTE: there are some extra pattern matchers on the request path of JVM PACT. I hadn't added them on the JS part as I was just getting started (I assume that shouldnt change how eachKeyLike works) JS code used to generate the contract Actual behaviour The PACTs should be identical for the eachkeylike section Steps to reproduce How can someone else reproduce this bug? The gist files has all the code required to reproduce this Relevant log files none Slack conversation pertaining to this issue pact-foundation/pact-js