Label Support with cypher queries about neo4j-js HOT 3 CLOSED

A better way would be, if you want labels in your query result, you need to specify that using cypher. for example:

MATCH n
RETURN n

would not get you labels, but if specify

MATCH n
RETURN n, labels(n)

then you will get labels. This way we're using cypher instead of another optional parameter, and you wouldn't have to make an extra round-trip to neo4j to get the labels.

The algorithm which parses the query result would need to be intelligent enough to look for column names matching labels(x) and interpret that column to be the labels for column x.

For full compatibility, you would need to parse the original return statement to see if there were any AS statements. For example:

MATCH n
RETURN n AS myNode, labels(n)

In this case, n would not be a column name because it was aliased to myNode, but the only way to know that is to check the original return statement.

As a first pass it probably isn't necessary to worry about this edge case though. You could get it working based on the first example, and then come back to this.

from neo4j-js.

And actually you can now create literal maps in cypher, e.g.

MATCH n
RETURN { data : n, labels: labels(n), id: id(n) } as node

from neo4j-js.

that solves the problem I was having. its not as necessary to code this now

from neo4j-js.