pact
Here are 114 public repositories matching this topic...
As part of the process of making the Pact docs more user friendly, we'd like to start writing feature documentation once, and providing code examples for each of the languages, rather than everyone having to write the same docs over and over again in each language.
The documentation for the consumer version selectors can be our first opportunity to give this approach a try. I have written the beh
enforce is currently strict in the error message, which means that e.g. using format to make an informative error is expensive even if the test passes.
-Dpact.rootDir="target/pact-classes" didn’t work for me.
env "pact.rootDir=target/pact-classes" bash did
...because of the "."
-
Updated
Jul 23, 2020 - Swift
-
Updated
Sep 3, 2020 - Java
-
Updated
Nov 28, 2019 - Java
-
Updated
Aug 3, 2020 - Kotlin
-
Updated
Apr 24, 2020
-
Updated
Aug 26, 2020 - TypeScript
-
Updated
Jun 2, 2020 - Java
-
Updated
Feb 19, 2019 - JavaScript
-
Updated
Apr 17, 2019 - Java
-
Updated
Feb 25, 2020 - Java
-
Updated
Aug 23, 2017 - JavaScript
-
Updated
Jul 25, 2020 - Go
-
Updated
Jun 9, 2020 - C#
-
Updated
Aug 4, 2020 - Java
-
Updated
Aug 18, 2020 - JavaScript
-
Updated
Jul 10, 2020 - Java
Improve this page
Add a description, image, and links to the pact topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the pact topic, visit your repo's landing page and select "manage topics."
As part of the process of making the Pact docs more user friendly, we'd like to start writing feature documentation once, and providing code examples for each of the languages, rather than everyone having to write the same docs over and over again in each language.
The documentation for the consumer version selectors can be our first opportunity to give this approach a try. I have written the beh