-
-
Notifications
You must be signed in to change notification settings - Fork 481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request body encoded for graphql content type #1371
Comments
I found the system property |
Could you provide the content type that is used by GraphQL? |
Sorry if that wasn't very clear but it's |
I'll add that to the list of json content types |
uglyog
pushed a commit
that referenced
this issue
Jun 4, 2021
This was referenced Jun 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Recently upgraded from Pact 3.6.2 to 4.1.21, everything looks ok except one test where graphql endpoint is used and the generated pact file uses encoded value for request body instead of actual graphql query. I'm guessing this isn't supported and is down to application/graphql being used instead of json, but is there any way to treat it like a text similar to json?
I'm using DSL to generate the RequestResponsePact and running with JUnit
The text was updated successfully, but these errors were encountered: