Skip to content
This repository has been archived by the owner on Sep 3, 2021. It is now read-only.

Unable to pass "null" values to custom cypher procedures #599

Open
lewisparma opened this issue Mar 22, 2021 · 1 comment
Open

Unable to pass "null" values to custom cypher procedures #599

lewisparma opened this issue Mar 22, 2021 · 1 comment

Comments

@lewisparma
Copy link

lewisparma commented Mar 22, 2021

After upgrading from 2.16.3 version to 2.19.2 we are no longer able to send null values to custom neo4j procedures.

Here are the params received through the graphql mutation:

{
  "name": "asd8",
  "settings": {
    serialNumber: '123456',
    ip: '10.0.0.1',
    **binding: null,**
    labels: [],
  }
}

And here is what neo4j-graphql-js sends downs:

CALL apoc.cypher.doIt("CALL custom.inventory.device.create($name, $settings.serialNumber,  $settings.ip, $settings.labels, $settings.binding) YIELD node RETURN node",...........
{
  "name": "asd8",
  "settings": {
    "serialNumber": "123456",
    "ip": "10.0.0.1",
    **"binding": {},**
    "labels": [],
  },
  "first": -1,
  "offset": 0,
}

As you can see null values are passed down as an empty map. We do not use auto generated mutations, they are manually defined and they just call the "neo4jgraphql" function.

@michaeldgraham
Copy link
Collaborator

#608

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants