[
https://issues.apache.org/jira/browse/TINKERPOP3-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP3-491:
----------------------------------------
Description:
[One|https://github.com/tinkerpop/tinkerpop3/blob/master/gremlin-groovy-test/src/main/groovy/com/tinkerpop/gremlin/process/graph/step/filter/GroovyExceptTest.groovy#L46]
of the tests uses the {code}.except(){code}/{code}.aggregate(){code} pattern.
There's an alternative way to get the same result:
{code}
g.V(v1Id).repeat(__.bothE('created').dedup().otherV()).emit().path()
{code}
It would be nice to see it a) added to the test cases and b) mentioned in the
docs. I bet for most people the {code}.dedup(){code} way is everything but
obvious.
was:
[One|https://github.com/tinkerpop/tinkerpop3/blob/master/gremlin-groovy-test/src/main/groovy/com/tinkerpop/gremlin/process/graph/step/filter/GroovyExceptTest.groovy#L46]
of the tests uses the {code}.except(){code}/{code}.aggregate(){code} pattern.
There's an alternative way to get the same result:
{code:groovy}
g.V(v1Id).repeat(__.bothE('created').dedup().otherV()).emit().path()
{code}
It would be nice to see it a) added to the test cases and b) mentioned in the
docs. I bet for most people the {code}.dedup(){code} way is everything but
obvious.
> Test case for a replacement of the except()/aggregate() pattern
> ---------------------------------------------------------------
>
> Key: TINKERPOP3-491
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-491
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: test-suite
> Reporter: Daniel Kuppitz
>
> [One|https://github.com/tinkerpop/tinkerpop3/blob/master/gremlin-groovy-test/src/main/groovy/com/tinkerpop/gremlin/process/graph/step/filter/GroovyExceptTest.groovy#L46]
> of the tests uses the {code}.except(){code}/{code}.aggregate(){code} pattern.
> There's an alternative way to get the same result:
> {code}
> g.V(v1Id).repeat(__.bothE('created').dedup().otherV()).emit().path()
> {code}
> It would be nice to see it a) added to the test cases and b) mentioned in the
> docs. I bet for most people the {code}.dedup(){code} way is everything but
> obvious.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
