JVM version of Pact. Enables consumer driven contract testing, providing a mock service and DSL for the consumer project, and interaction playback and verification for the service provider project.
The issue comes from the constraint that the consumer and the provider should use pact specification version 2. This results in a pact verification warning about the number attribute:
I am trying to create a contract for a response which contains a number value attribute. Something like the following:
The used matchers for this part of the response are the following:
And the result in the pact itself:
The issue comes from the constraint that the consumer and the provider should use pact specification version 2. This results in a pact verification warning about the number attribute:
What is the best approach for number type matchers when using pact specification version 2? Is there any way the resulting matcher to be:
The same as the one which comes as a result when stringType() is used.