diff --git a/multi/multi__contract_dsl.html b/multi/multi__contract_dsl.html index 95a23a280e..7bbfaf967d 100644 --- a/multi/multi__contract_dsl.html +++ b/multi/multi__contract_dsl.html @@ -1097,21 +1097,21 @@ dynamic parts of a contract.
You can use the Currently, Spring Cloud Contract Verifier supports only JSON Path-based matchers with the
-following matching possibilities: Groovy DSL For the stubs: For the verification: Groovy DSL For the stubs(in tests on the Consumer’s side): For the verification(in generated tests on the Producer’s side): You can use the Currently, Spring Cloud Contract Verifier supports only JSON Path-based matchers with the
-following matching possibilities: Groovy DSL For the stubs: For the verification: Groovy DSL For the stubs(in tests on the Consumer’s side): For the verification(in generated tests on the Producer’s side):bodyMat
You can set it in the request or inputMessage part of your contract.response or outputMessage side of the
contract.byEquality(): The value taken from the response via the provided JSON Path must be
-equal to the value provided in the contract.byRegex(…): The value taken from the response via the provided JSON Path must
-match the regex.byDate(): The value taken from the response via the provided JSON Path must
-match the regex for an ISO Date value.byTimestamp(): The value taken from the response via the provided JSON Path must
-match the regex for an ISO DateTime value.byTime(): The value taken from the response via the provided JSON Path must
-match the regex for an ISO Time value.byEquality(): The value taken from the response via the provided JSON Path must be
-equal to the provided value in the contract.byRegex(…): The value taken from the response via the provided JSON Path must
-match the regex.byDate(): The value taken from the response via the provided JSON Path must match
-the regex for an ISO Date value.byTimestamp(): The value taken from the response via the provided JSON Path must
-match the regex for an ISO DateTime value.byTime(): The value taken from the response via the provided JSON Path must match
-the regex for an ISO Time value.byType(): The value taken from the response via the provided JSON Path needs to be
+following matching possibilities:byEquality(): The value taken from the consumer’s request via the provided JSON Path must be
+equal to the value provided in the contract.byRegex(…): The value taken from the consumer’s request via the provided JSON Path must
+match the regex.byDate(): The value taken from the consumer’s request via the provided JSON Path must
+match the regex for an ISO Date value.byTimestamp(): The value taken from the consumer’s request via the provided JSON Path must
+match the regex for an ISO DateTime value.byTime(): The value taken from the consumer’s request via the provided JSON Path must
+match the regex for an ISO Time value.byEquality(): The value taken from the producer’s response via the provided JSON Path must be
+equal to the provided value in the contract.byRegex(…): The value taken from the producer’s response via the provided JSON Path must
+match the regex.byDate(): The value taken from the producer’s response via the provided JSON Path must match
+the regex for an ISO Date value.byTimestamp(): The value taken from the producer’s response via the provided JSON Path must
+match the regex for an ISO DateTime value.byTime(): The value taken from the producer’s response via the provided JSON Path must match
+the regex for an ISO Time value.byType(): The value taken from the producer’s response via the provided JSON Path needs to be
of the same type as the type defined in the body of the response in the contract.
byType can take a closure, in which you can set minOccurrence and maxOccurrence.
That way, you can assert the size of the flattened collection. To check the size of an
-unflattened collection, use a custom method with the byCommand(…) testMatcher.byCommand(…): The value taken from the response via the provided JSON Path is
+unflattened collection, use a custom method with the byCommand(…) testMatcher.byCommand(…): The value taken from the producer’s response via the provided JSON Path is
passed as an input to the custom method that you provide. For example,
byCommand('foo($it)') results in calling a foo method to which the value matching the
JSON Path gets passed. The type of the object read from the JSON can be one of the
diff --git a/single/spring-cloud-contract.html b/single/spring-cloud-contract.html
index 9ca99bcd78..af572dd905 100644
--- a/single/spring-cloud-contract.html
+++ b/single/spring-cloud-contract.html
@@ -4497,21 +4497,21 @@ dynamic parts of a contract.bodyMat
You can set it in the request or inputMessage part of your contract.response or outputMessage side of the
contract.byEquality(): The value taken from the response via the provided JSON Path must be
-equal to the value provided in the contract.byRegex(…): The value taken from the response via the provided JSON Path must
-match the regex.byDate(): The value taken from the response via the provided JSON Path must
-match the regex for an ISO Date value.byTimestamp(): The value taken from the response via the provided JSON Path must
-match the regex for an ISO DateTime value.byTime(): The value taken from the response via the provided JSON Path must
-match the regex for an ISO Time value.byEquality(): The value taken from the response via the provided JSON Path must be
-equal to the provided value in the contract.byRegex(…): The value taken from the response via the provided JSON Path must
-match the regex.byDate(): The value taken from the response via the provided JSON Path must match
-the regex for an ISO Date value.byTimestamp(): The value taken from the response via the provided JSON Path must
-match the regex for an ISO DateTime value.byTime(): The value taken from the response via the provided JSON Path must match
-the regex for an ISO Time value.byType(): The value taken from the response via the provided JSON Path needs to be
+following matching possibilities:byEquality(): The value taken from the consumer’s request via the provided JSON Path must be
+equal to the value provided in the contract.byRegex(…): The value taken from the consumer’s request via the provided JSON Path must
+match the regex.byDate(): The value taken from the consumer’s request via the provided JSON Path must
+match the regex for an ISO Date value.byTimestamp(): The value taken from the consumer’s request via the provided JSON Path must
+match the regex for an ISO DateTime value.byTime(): The value taken from the consumer’s request via the provided JSON Path must
+match the regex for an ISO Time value.byEquality(): The value taken from the producer’s response via the provided JSON Path must be
+equal to the provided value in the contract.byRegex(…): The value taken from the producer’s response via the provided JSON Path must
+match the regex.byDate(): The value taken from the producer’s response via the provided JSON Path must match
+the regex for an ISO Date value.byTimestamp(): The value taken from the producer’s response via the provided JSON Path must
+match the regex for an ISO DateTime value.byTime(): The value taken from the producer’s response via the provided JSON Path must match
+the regex for an ISO Time value.byType(): The value taken from the producer’s response via the provided JSON Path needs to be
of the same type as the type defined in the body of the response in the contract.
byType can take a closure, in which you can set minOccurrence and maxOccurrence.
That way, you can assert the size of the flattened collection. To check the size of an
-unflattened collection, use a custom method with the byCommand(…) testMatcher.byCommand(…): The value taken from the response via the provided JSON Path is
+unflattened collection, use a custom method with the byCommand(…) testMatcher.byCommand(…): The value taken from the producer’s response via the provided JSON Path is
passed as an input to the custom method that you provide. For example,
byCommand('foo($it)') results in calling a foo method to which the value matching the
JSON Path gets passed. The type of the object read from the JSON can be one of the
diff --git a/spring-cloud-contract.xml b/spring-cloud-contract.xml
index 93970f6765..8498561bfd 100644
--- a/spring-cloud-contract.xml
+++ b/spring-cloud-contract.xml
@@ -7399,62 +7399,62 @@ following matching possibilities: