Add audit for variable coercion failure

[trevor-scheer]

From the spec:

If CoerceVariableValues() raises a GraphQL request error, the server SHOULD NOT execute the request and SHOULD return a status code of 400 (Bad Request).

Fixes #57

Should I be also "should not"ing the request execution (and how can I accomplish that)?
I'm assuming I don't update the audit results (it looks like that's in a GH workflow) but let me know if there are any other changes that should come with PR.

[enisdenjo]

Hey sorry, I haven't forgotten about this. Am currently on a break until next week - I'll review this properly then, thanks!

[enisdenjo]

Please rebase this PR on main because #29 should be fixed now.

[trevor-scheer]

@enisdenjo looks like the same needs to be done here as well?

graphql-http/.github/workflows/continuous-integration.yml

Line 7 in a51dffb

pull_request:

[enisdenjo]

Not really, the CI does not change anything - its just checks.

[trevor-scheer]

@enisdenjo ok. I only said that because the some of the statuses were expected but didn't seem to be running. It looks like everything's passed now.

[enisdenjo]

I only said that because the some of the statuses were expected but didn't seem to be running

Yeah, the workflows have to be triggered manually for first-time contributors. But I think I'll add it still to avoid having the WFs manipulated by PRs. 🤔

[enisdenjo]

Thank you! This is great, I just added the same test but for application/json.

[enisdenjo]

🎉 This PR is included in version 1.17.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀