Hi team, I’m curious about the future plans for pa...
# pactflow-ama
i
Hi team, I’m curious about the future plans for pact-php. Specifically, I’d like to know if there’s any roadmap or timeline for supporting v4 of the Pact specification directly in pact-php. Additionally, is there any plan to make v4 support available without relying on beta features or the FFI wrapper? It would be great to understand how this aligns with the broader vision for Pact language support. Looking forward to your insights!
y
it is already supported in v10 of pact-php and it is GA now https://github.com/pact-foundation/pact-php?tab=readme-ov-file#compatibility the ffi wrapper is integral to the client libraries capabilities, and there is no appetite from the core team to see to create pure implementations that adhere to the specification but do not rely on the rust shared core which is accessible vis FFI. it is what gives pact-php the ability to create and verify Pacts up to and including v4
m
Thanks Yousaf.
P.S. Pact PHP is not part of PactFlow, it’s a part of the wider Pact Open Source community.
i
Thanks guys for answers.
@Matt (pactflow.io / pact-js / pact-go) "P.S. Pact PHP is not part of PactFlow, it’s a part of the wider Pact Open Source community." Does this mean it is not possible to use Bi-directional Contract Testing with PHP?
y
you can create consumer pacts created by pact-php and upload the consumer contract to pactflow. which can then be used by either Pacts traditional verification or via bi-directional if you upload a provider contract ( oas + test evidence )
i
is there any example project for this?
y
we dont have php examples https://docs.pactflow.io/docs/examples its very generic though so you should be able to piece together