Looking integrate `pact` with `nestjs`, but it loo...
# pact-jsj
Jonathan Chapman
03/28/2024, 4:02 PMLooking integrate
pactnestjsnestjs-pactm
Matt (pactflow.io / pact-js / pact-go)
03/29/2024, 5:12 AM
@Omer Morad mind weighing in here please?
j
Jonathan Chapman
04/03/2024, 12:03 AM@Omer Morad don't want to push too hard, we are all busy but it would be nice to get an answer on this
o
Omer Morad
04/03/2024, 5:03 AMHey @Jonathan Chapman
Sorry! I’m on vacation :)
What do you mean by outdated? Are you talking about the package dependencies?
j
Jonathan Chapman
04/03/2024, 6:44 AMSorry to disrupt vacation.
Jonathan Chapman
04/03/2024, 6:45 AMIt looks like it's on Pact V2, and Pact is on V4 now.
Will there be support for the next versions of Pact?
y
Yousaf Nabi (pactflow.io)
04/03/2024, 11:25 AM
we would welcome pull requests if you are interested in adding support. It would be nice to cater for the V2, V3 and V4 interfaces, however if its possible to use pact-js directly, this negates the need to use a package which consumes pact-js, and requires the need to be kept in lockstep with feature parity.
personally my preference would be to use pact-js over the variants as the lifecycle of a pact test with the rust core versus the ruby core, mean many of the boilerplate challenges of writing a test are covered. It’s reduces the surface area for maintainers as well
j
Jonathan Chapman
04/03/2024, 10:26 PMWell, I see a V3 PR in there today that passes all the tests, and it's been sitting there since December. So, are you guys actively paying attention to the repo?
I do agree with your preference for using
pact-jspact-jsy
Yousaf Nabi (pactflow.io)
04/03/2024, 11:12 PM
you could have reviewed the pr? its a breaking change for existing users, I’ve added my thoughts
Yousaf Nabi (pactflow.io)
04/03/2024, 11:15 PM
you can as an interim measure fork the project, implement and test your required changes and contribute them back. your additional end user testing adds gravitas to the changes being sound. ( you can yarn link local projects to test them out or publish to npm under a personal scope if you need global access )
you aren’t blocked by maintainers not moving the project forward, there are a myriad of reasons why they may not be driving something forward but that is no reason why others cant.
the pr sitting there since December isn’t great, it’s slipped my radar as it isn’t a project I’m across often.