Add end node operator to path expander label filter #327
Conversation
This file contains 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
|
This fulfills feature request #325 |
sarmbruster
approved these changes
Mar 19, 2017
|
thanks @InverseFalcon for your PR. |
jexp
pushed a commit
that referenced
this pull request
Apr 3, 2017
* Add end node operator to path expander label filter * Updated end node operator in the code and tests
vga91
added a commit
that referenced
this pull request
Feb 16, 2023
ncordon
pushed a commit
to ncordon/neo4j-apoc-procedures
that referenced
this pull request
Nov 1, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The new operator,
>, works just like the termination operator/in that labels in the filter will be used as end nodes in the expansion, except traversal is allowed past these end nodes.The new
limitconfig parameter applies when using this filter.