Not to detract from Adam’s epic announcement about a Planned release of PactNet 4.0.0 on 6th June 2022 🚀 but this one almost slipped me by, so want to make sure it doesn’t slip you by.❣️ 🚨 Using Wiremock & .NET. 🔥 Now you can generate Pact 🔗 contracts from your Wiremock Server 👉 Check it out here https://lnkd.in/eKagaDHn 📖 Background https://lnkd.in/egczVAex 😍 Thanks Stef Heyenrath for the work, Bas Dijkstra for the connection and Tom Akehurst for creating wiremock in the first place

I've had a chance to quickly review this and I'm not sure how useful it really is. It doesn't support matchers, which is the real key thing you need. They've also confused some terminology, because they use Given to specify the request, whereas in the Pact DSL that's actually used for configuring provider states.

Hey Adam, thanks for taking a look. this would be used in the bi-directional flow only, whereby matchers, and providers states are not supported, as the verification would be performed against an OAS, rather than using a Pact verifier against the running provider. So they wouldn't get as strong guarantees as CDCT but enables them to reuse existing Wiremock implementations. Feedback on the DSL is good though 👍 I can see how that could cause additional confusion. I've already seen a couple of cases of people using the alternate modes of Pact file generation (adapters, not native Pact implementations) with CDCT, and they've seen the issues that matchers/provider states were designed to prevent. Will make sure when we get this added to the docs, that we get some additional notes around that.