Add PathNamePattern class and corresponding pathName() function to allow constructing queries with named paths #179
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…low constructing queries with named paths, like "MATCH p=(n)-[]-()".
Author
|
@jamesfer any chance that you might look at this soon? If you prefer an alternative way to enable named paths, I'd offer to implement that too. |
databu
force-pushed
the
path-name-pattern
branch
from
08775cf to
606cbe0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add PathNamePattern class and corresponding pathName() function to allow constructing patterns with named paths, like "MATCH p=(n)-[]-()".
(This was previously in PR #163 which I closed because our master branch got polluted with other changes.)