Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: path groups #26

Closed
robobenklein opened this issue Mar 24, 2023 · 3 comments
Closed

Feature request: path groups #26

robobenklein opened this issue Mar 24, 2023 · 3 comments
Labels
enhancement New feature or request

Comments

@robobenklein
Copy link

For example, the syntax:

MATCH p=(n1 {type: "compilation_unit"})-[]->(n2 {type: "class_declaration"})-[*2]->(n3 {type: "method_declaration"})-->(n4 {text: "Main", type:"identifier"})
RETURN p

The return type for a path from neo4j has start, end, segments, and notably includes nodes or edge that would be traversed by the edge * operator.

I can still work around it, but I would very much like to have access to variable-length paths!

@j6k4m8
Copy link
Member

j6k4m8 commented Mar 24, 2023

Hey @robobenklein! Thanks for the comment, and yes this sounds like a great feature addition! Adding to our backlog :)

@j6k4m8 j6k4m8 added the enhancement New feature or request label Mar 24, 2023
j6k4m8 pushed a commit that referenced this issue Feb 15, 2024
* Add path groups #26, #35

* Remove unnecessary enumerate

* Update CHANGELOG and bump version in setup.py
@davidmezzetti
Copy link
Contributor

@j6k4m8 - I believe this can be closed as fixed with #37?

@j6k4m8
Copy link
Member

j6k4m8 commented Feb 17, 2024

Yes confirmed! Thank you @davidmezzetti !!

@j6k4m8 j6k4m8 closed this as completed Feb 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants