-
Notifications
You must be signed in to change notification settings - Fork 146
Support for Neo4j v3.4.0 #53
Comments
Thanks for reporting @cooperka This seems to be a bug in APOC and will need to be fixed there. I've opened this issue in APOC to track: neo4j-contrib/neo4j-apoc-procedures#819 |
Thanks @johnymontana! Sadly those issues doesn't look very active at all 😿 Is there anywhere (e.g. README) that documents the current Neo4j version supported by this lib? Might be good to point this out so new users aren't confounded. |
I just upgraded to 3.4.1 in Neo4j Desktop and with APOC 3.4.0.1, and this type of @cypher directive is working as expected, without "Type mismatch: expected List" |
Thanks for the update @Yuri2b! It looks like CircleCI is already using APOC v3.4.0.1 and still failing with the same error (see Edit: It's on Neo4j 3.4.0; I submitted a PR to upgrade that so we'll see. |
Verified successful. I'll let that PR automatically close this issue on merge. Thanks again @Yuri2b. |
I hadn't realized this was resolved in Neo4j 3.4.1 - we were planning a workaround fix in APOC, but great to see it resolved in Neo4j. It seems one unrelated 3.4 integration test is still failing (which I'll fix tomorrow), but the others look good. |
I just upgraded to Neo4j v3.4.0 and some queries no longer work. It looks like this lib is already being tested on v3.4.0 but tests are failing with the same error I'm getting. It seems related to the use of
@cypher
directives.Example errors, taken from my own app as well as the CI tests here:
My schema:
Leads to:
integration › Handle @cypher directive on QueryType:
integration › GraphQL query with @cypher directive:
The text was updated successfully, but these errors were encountered: