Ronald Holshausen
Ronald Holshausen
The key is calculated, if it is not already set. It will be based on the contents, and will be sensitive to the order of things. So either the contents...
BTW, the key is designed to be set by the user, and is only calculated if not set. It is to provide a unique identifier within the Pact file. Having...
Provider states were designed to support the same description and different parameters. Think of a state `a user exists` with 3 different sets of parameters with user data. You would...
Is it forcing the output to V2 format?
@Kampfmoehre That is wrong, there are only matching rules for the body ``` "matchingRules": { "body": { "$.name": { "combine": "AND", "matchers": [ { "match": "type" } ] } }...
The matching rules for the metadata are not being created in the Pact file.
The problem is that to know if it can inject an HTTP request, it needs to know the type of the interaction, but there is no Pact files, so it...
I've just checked the [GraphQL spec](https://graphql.org/learn/serving-over-http/), the recommendation when using it over HTTP is to use JSON encoded bodies. Is this not the case for you? What format is being...
Can you provide the full stack trace?
Found the issue. If you change it to ``` System.setProperty("pact.content_type.override.application\\graphql", "text") ``` it should work. But I will fix that.