[
https://issues.apache.org/jira/browse/TINKERPOP-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15655657#comment-15655657
]
ASF GitHub Bot commented on TINKERPOP-1545:
-------------------------------------------
Github user okram commented on the issue:
https://github.com/apache/tinkerpop/pull/486
`PathProcessors` are intended for path analysis steps that use
`by()`-modulation. Also, what about `CyclicPathStep`? Perhaps just itemize
those steps explictly for now and now have them implement `PathProcessor`.
However...I guess they are `PathProcessors` that don't project out...
hmmm... perhaps do a study of `PathProcessor` use and see if making
`SimplePathStep` and `CyclicPathStep` one of those would be a problem.
> IncidentToAdjacentStrategy is buggy
> -----------------------------------
>
> Key: TINKERPOP-1545
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1545
> Project: TinkerPop
> Issue Type: Bug
> Affects Versions: 3.1.4, 3.2.3
> Reporter: Daniel Kuppitz
> Assignee: Daniel Kuppitz
>
> {{IncidentToAdjacentStrategy}} turns {{outE().inV().simplePath()}} into
> {{out().simplePath()}}, which will return a wrong result as soon as there is
> more than 1 edge between a pair of vertices.
> The set {{INVALIDATING_STEP_CLASSES}} should only contain
> {{PathProcessor.class}} and {{LambdaHolder.class}} Furthermore
> {{SimplePathStep}} should implement {{PathProcessor}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
