Nested arrays are not parsed into Neo4jNode class about neo4j-fiber HOT 10 CLOSED

Hello @bummo ,

Could you please provide sample data, and a cypher query, which causes such results

from neo4j-fiber.

Any data, query is simply
var d = db.query("MATCH (n) RETURN collect(n)").fetch()[0];
console.log(d); // { 'collect(n)': [{...},{...}] }

Just noticed other issue:
If I give an alias to the collection e.g "MATCH (n) RETURN collect(n) as nodes" the result is
{ nodes: undefined }

from neo4j-fiber.

Hello @bummo ,

Sorry for delay with publish, faced hardware malfunction, had to fix my old Mac.

Please test it on your end, let me know if it's solved for you

from neo4j-fiber.

Hi @dr-dimitru,

I think we are getting there, however, the collect function now returns a Neo4jNode Class, which is again not what expected because the query has been run with '.fetch()' so the outcome should not be a cursor.
So for every collect query an iterative '.get()' function has to be called to get the actual node.

Let me know if this is going to be complicated & Thanks for update

from neo4j-fiber.

Hello @bummo ,

You're right, going to fix it now

from neo4j-fiber.

Hello @bummo ,

Should be fixed now, feel free to reopen this issue.
Thank you for your patience.

from neo4j-fiber.

Thanks @dr-dimitru, works nicely.

I've just noticed that labels are returned as an indexed object rather than an array of strings, not a big deal of course, just a remark.

from neo4j-fiber.

Hello @bummo ,

labels are returned as an indexed object rather than an array of strings

With the same query?

MATCH (n) RETURN collect(n)

from neo4j-fiber.

@dr-dimitru apologies... my debugger considers Arrays as Objects. (which is technically true)

from neo4j-fiber.

@bummo no worries, thank you for contribution.

from neo4j-fiber.