-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pact V3 support #199
Comments
Thanks for raising this! This has been asked before (although not tracked here) on pact-foundation/pact-js#483 . At the time, my thinking was we'd add it when the V3 branch is ready for production use, but I feel like more and more people are using V3 now. I think it might be better to support it, and instead chase down the remaining issues that prevent V3 being recommended for production. |
Update: I've published a draft of a V3 compatible jest-pact. You can pick it up at:
Unfortunately, the interface had to change a bit. You can see a usage example in the readme at: https://github.com/pact-foundation/jest-pact/tree/pact-js-v3#pact-js-v3 I'm not certain about the interface yet, feedback very welcome. |
@brendan-donegan Did you try out the V3 |
We are working with the 0.9.0-beta.v3 right now and it works very well in all of our contract cases. Thank you for suporting the V3 Specification. Do you think there will be a release with the v3 specification soon? We had an issue after the release of 9.0.0 two days ago: While using the "^0.9.0-beta.v3" syntax, the package manager fetched the 9.0.0 instead of the current V3 beta. So we had to use the fixed version 0.9.0-beta.v3. |
Ah, yes, good point. I’d like to include both, but it’s a bit tricky before the beta pact-js branch is merged, because of the peer dependency.
We’re working on the V3 merge as the highest priority right now.
…Sent from my mobile
On 10 May 2021, at 7:12 pm, schowave ***@***.***> wrote:
We are working with the 0.9.0-beta.v3 right now and it works very well. Thank you for suporting the V3 Specification. Do you think there will be a release with the v3 specification soon?
We had an issue after the release of 9.0.0 two days ago: While using the "^0.9.0-beta.v3" syntax, the package manager fetched the 9.0.0 instead of the current V3 beta. So we had to use the fixed version 0.9.0-beta.v3.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Are there any Updates on the V3 merge? |
We have the provider since nearly done, but there's still work to do on the consumer side. You can follow along with the project here https://github.com/pact-foundation/pact-js/projects/3, or join us on slack if you would like to help out |
(I think Matt and I are working on it in pretty much all the spare time we have available for software dev) |
Great stuff here @TimothyJones & @mefellows How have people been finding the new interface? |
There are still some minor teething issues/bugs to sort out in the main Pact JS project, and we currently don't have message support (see https://github.com/pact-foundation/pact-js/projects/3). The JS core now has all of the requisite APIs for Pact JS, so it's just a public API implementation now mainly to go. |
mainlined into master for jest-pact |
It is probably a good idea to release a 1.0 of jest pact soon |
Will close this now, feedback can be provided in this issue Thanks for everyones help |
Hi,
We are using jest-pact in our project and would like to leverage some of the new features in Pact v3. I was wondering if/when v3 support could be added in jest-pact?
The text was updated successfully, but these errors were encountered: