Closed TimothyJones closed 1 year ago
Thanks for raising/moving this here Tim.
The pact-core
package release just went out with the new fix. This will come in by default based on our dependency rules, but next change we can enforce that too.
As for the functions, I'm confused about how we support the (intended) eachKeyLike
function (matching keys, not values), so will need some support on how we implement that from @uglyog. Will use this ticket to track that activity.
Update on this issue. eachKeyLike
should use set pact:matcher:type: "eachKey"
as documented here: https://github.com/pact-foundation/pact-reference/blob/master/rust/pact_ffi/IntegrationJson.md
👋 Hi! The 'smartbear-supported' label has just been added to this issue, which will create an internal tracking ticket in PactFlow's Jira (PACT-784). We will use this to prioritise and assign a team member to this task. All activity will be public on this ticket. For now, sit tight and we'll update this ticket once we have more information on the next steps.
See our documentaiton for more information.
👋 Hi, There has been no changes related to this issue, #662 and #1077 - is there anything I can do so that this bug will be addressed?
You could submit a PR to fix it?
Software versions
Please provide at least OS and version of pact-js
Issue Checklist
Please confirm the following:
Expected behaviour
As per https://github.com/pact-foundation/pact-reference/issues/216 ,
eachLike
doesn't match correctly. This object:should be matched by
Actual behaviour
It is not matched - the match only applies at the first level.
Steps to reproduce
As above
Extra information
To get the fix, we'll need to bump the rust core to at least 0.3.12.
Also, as @uglyog pointed out:
Probably the right fix for this is:
eachKeyLike
toeachValueLike
eachKeyLike
matcher (this is a breaking change, since the signature foreachKeyLike
would describe something different to what it currently does / and currently is documented to do)eachKeyValueLike
matcher which could be added