Is it still the case that Pact-net can't use V4 Pa...
# pact-net
b
Is it still the case that Pact-net can't use V4 Pact files in Provider tests? Or is that inaccurate?
Did a quick search and it seems like it is that way still.
m
It can verify Pact V4, but can’t generate them (at the present moment, to my knowledge)
As long as you only have HTTP interactions, or message interactions it should be OK
(i.e. you can’t have plugin interactions just yet)
y
Hey Matt, I am curious what is the current situation like with PactNet and if there is any plan to support Pact Specification v4 ? The reason I am asking is that we are considering to use Pact for contract validation for our .NET services. Some of the services use GRPC + Protobuf, but if I understand correctly for that to work the pact library should support v4 specification first ?
m
We would like to add support but we don’t have current timelines/plans. We will need to coordinate with @Adam Rodger (pact-net) and create a clearer implementation guide for maintainers before this work can happen.
y
Thanks for the response. Do you know if there is any work-around at the moment ?
m
I think you could run the native verifier: https://docs.pact.io/implementation_guides/cli#native-binary-new
👍 1
(if it’s just provider side verification)
if you need to do the consumer side, you can, but it’s a lot more work (see https://docs.pact.io/implementation_guides/other_languages#native-c-interface-integration-v2v3v4-specification-support)
y
Thanks for the links, I think the native C interface link is broken
m
Thanks, i’ll update that now.