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

Separate map/flatmap coverage from coverage of lambda functions. #145

Open
krlawrence opened this issue Apr 7, 2019 · 0 comments
Open

Comments

@krlawrence
Copy link
Owner

krlawrence commented Apr 7, 2019

Currently the map and flatMap coverage is nested inside the coverage of Groovy lambdas. That made sense when just discussing TinkerGraph but now more and more people connect to a Gremlin Server it would make more sense to have map and flatMap moved up a level and just cover lambda specific examples in their current location.

Also add an example of checking an edge property inside a flatMap but only passing the incident vertex onto the next step.

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

1 participant