Also, verification fails if there are no pacts to ...
# pact-js
a
Also, verification fails if there are no pacts to verify when it used to pass with ^9.0.0. The provider does exist, there but given the consumerVersionSelectors there are no pacts to verify yet:
Copy code
{
      publishVerificationResult: false,
      provider: 'delivery-promise-service',
      providerBaseUrl: '<http://localhost:8000>',
      providerVersion: '09fe6815',
      providerBranch: 'DP-2086-state-handlers-for-rob-contracts',
      pactBrokerUrl: '<https://pact-broker.dunelm.io/>',
      enablePending: true,
      consumerVersionSelectors: [
        { mainBranch: true },
        { deployedOrReleased: true },
        { matchingBranch: true }
      ],
      customProviderHeaders: { 'x-apigateway-event': '""', 'x-apigateway-context': '""' }
}
Untitled.sh
m
Thanks Adam. Could you please raise an issue? We'll get it added to the core so other languages can benefit also
It probably should be an explicit behaviour rather than assumed (it may not be expected to find no pacts)
a
Will raise it now 👍 Where do you want it raising? pact-js, pact-js-core?
y
When Matt is referring to the core, he may be referring to the rust-core rather than pact-js-core. If you raise against pact-js for now, we can sort out any further issues in other repos if req 👍
thx again fella
a
Awesome thanks both 🙂
m
yep, raise with JS for now and we’ll always move it to the right place. Your raising it is the key thing!
🙌 1