You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Node/Relationship.where method is implemented returning PatternElement. Can it return Node/Relationship, similar to Node/Relationship.withProperties?
This is to allow constructing such Node/Relationship in a separate method, to be able to use it where Node/Relationship is expected, not only in match clause.
The simplest way to do this seems to be moving PatternElement.where to ExposesProperties.
The text was updated successfully, but these errors were encountered:
Ok, it's possible to cast it in the current version.
My point is that users could expect the same behavior for both withProperties and where, because both specify where conditions. Although with a different Cypher syntax.
withProperties and where are almost the same, with a slight conceptual difference that node.where(node...) requires a named node already. Potentially there could be another overloaded where method with lambda (Consumer) argument. Or it could even be the only method, to prevent devs from the mistake of passing another node instance or an arbitrary condition irrelevant to the node.
Hi,
Currently
Node/Relationship.where
method is implemented returningPatternElement
. Can it returnNode/Relationship
, similar toNode/Relationship.withProperties
?This is to allow constructing such
Node/Relationship
in a separate method, to be able to use it whereNode/Relationship
is expected, not only inmatch
clause.The simplest way to do this seems to be moving
PatternElement.where
toExposesProperties
.The text was updated successfully, but these errors were encountered: