When a boolean parameter to a cypher directive is false NULL is inserted instead about graphql HOT 5 CLOSED

Hi, @mjfwebb. Sorry, you have to pass the argument through as true otherwise you get the same error

mutation {
  createTests(input: { _emptyInput: true }) {
    tests {
      test(value: true)
    }
  }
}

from graphql.

Many thanks for raising this bug report @michaeldaudiolo. 🐛 We will now attempt to reproduce the bug based on the steps you have provided.

Please ensure that you've provided the necessary information for a minimal reproduction, including but not limited to:

• Type definitions
• Resolvers
• Query and/or Mutation (or multiple) needed to reproduce

If you have a support agreement with Neo4j, please link this GitHub issue to a new or existing Zendesk ticket.

Thanks again! 🙏

from graphql.

Hi @michaeldaudiolo! I'm running through your reproduction steps and I received an error on the first mutation that you wrote:

mutation {
  createTests(input: { _emptyInput: true }) {
    tests {
      test
    }
  }
}

Response:
"Cannot return null for non-nullable field Test.test."

Do you not receive the same response?

from graphql.

We've been able to confirm this bug using the steps to reproduce that you provided - many thanks @michaeldaudiolo! 🙏 We will now prioritise the bug and address it appropriately.

from graphql.

The fix for this issue is released on version 5.2.0, please be aware of another issue we found during the reproduction of this: #4838 that is still to be fixed.

from graphql.