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

Traversal inside by modulator - section 3.3.2 #98

Closed
rengel-de opened this issue Jun 14, 2018 · 2 comments
Closed

Traversal inside by modulator - section 3.3.2 #98

rengel-de opened this issue Jun 14, 2018 · 2 comments

Comments

@rengel-de
Copy link

In section 3.3.2 the book says (emphasis mine):

To demonstrate that just about any arbitrary traversal can be placed inside the by modulator here
is one more example that counts the number of outgoing routes for the source and destination
airports as part of generating the path result.

g.V(3).out().limit(5).path().by(out().count().fold())

As I understand it (so far), out().count().fold() is not a traversal because it does not start with g.V() or g.E(). Used on its own, out().count().fold() produces only [0]. Or is any syntactically valid sequence of steps a traversal?

Would it be correct to say that such an inner (my term) or embedded traversal takes its input from the outer traversal up to the position of the embedded traversal?

@krlawrence
Copy link
Owner

krlawrence commented Jun 15, 2018

I'll think about possible wording improvements. The key point is that it can be more than just a property key. These types of traversal are often referred to as "anonymous" traversals. Thanks for the feedback.

@krlawrence
Copy link
Owner

Fixed in release 280

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants