Chris
03/27/2024, 10:26 PMcan-i-merge
with monorepos, where that monorepo contains consumers and providers, and each consumer & provider has its own build pipeline? Our usual pattern is for work to be done on both ends out of the one branch. The problem comes when we run can-i-merge
on the the answer is always no because the provider work (part of the same branch) is not yet merged to the main branch.Eric Rollins
03/28/2024, 1:28 PMJoão Miguel Rocha
03/28/2024, 3:32 PMLyubomir Stoimchev
03/29/2024, 12:56 PMitems:
nullable: true
Working (yaml OAS):
items:
type: array
nullable: true
Is there a way fix this without having to manually edit the OAS yaml file?Andrew Maxwell
04/02/2024, 9:18 AMconsumerVersionSelectors
option, but I am getting an error from pact_verifier
reporting "_cannot specify the field mainBranch with the field deployedOrReleased_".
I was wondering if there is a reason why this is not allowed?Mahesh Damavarapu
04/02/2024, 12:16 PM2024-04-02T12:13:50.251575Z ERROR ThreadId(09) pact_verifier: Failed to load pact - Failed to load pact from '<http://localhost:9292>'
I am able to see the consumer contract is available in the fetched path.
Any help here pleasePriyaranjan Mudliar
04/04/2024, 6:59 AMmatchingBranch: true
in there configuration ?Ratna Jenisha
04/04/2024, 12:30 PMJoel Whalen
04/04/2024, 2:27 PM--entrypoint
with pact_verifier_cli [OPTIONS]
?Michael Strasser
04/05/2024, 6:28 AMFábio Rodrigues
04/05/2024, 1:00 PMUlises Cervino
04/08/2024, 11:48 AMGowtham G
04/08/2024, 12:55 PMYair Shkedi
04/09/2024, 7:31 AM{
a: int //mandatory
b: int //optional
}
What is the best practice, to create 1 test that cover all the DTO or 2 tests, one for all the parameters, and the second with the mandatory only?
I am afraid from overhead, in case I have multiple optional, should I cover all the permutation??!!
Thanks in advanceMichael Schmidt
04/10/2024, 6:00 AMFábio Rodrigues
04/10/2024, 10:42 AMLaurence Cruz
04/10/2024, 6:33 PMRouaa Ben Ayed
04/11/2024, 3:52 PMJo Laing
04/11/2024, 3:55 PMWe are thrilled to announce the release of Pact Python `v2.2`, a significant milestone that not only improves upon the existing features but also offers an exclusive preview into the future of contract testing with Python.Be sure to read about at pact-pythons new doc site, in its inaugural blog post from @Joshua Ellis pact
Tim Vahlbrock
04/16/2024, 12:34 PMTim Vahlbrock
04/16/2024, 1:12 PMMatt (pactflow.io / pact-js / pact-go)
Tim Vahlbrock
04/17/2024, 6:19 AMOlúwátóósìn Anímáṣahun
04/17/2024, 9:19 AMTim Vahlbrock
04/17/2024, 10:04 AMTim Vahlbrock
04/17/2024, 10:39 AMMatt (pactflow.io / pact-js / pact-go)
Tim Vahlbrock
04/17/2024, 10:51 AMaofadero
04/17/2024, 3:18 PMBogdan Barliga
04/25/2024, 11:03 AM