> Is the objection to order(SearchAlgo) that it overloads order() or an
objection to specifying, DFS/BFS in the traversal itself?
for me, order() is a step. not a modulator. making it work as presented in
the pull request conflates those two concepts which i think is confusing (i
don't think we d
Hi,
Is the objection to order(SearchAlgo) that it overloads order() or an
objection to specifying, DFS/BFS in the traversal itself?
If so I do not really see how it is misplaced from a usability/API
perspective. Seems pretty natural to me and very graphy at that.
As mentioned earlier I am not
Github user spmallette commented on the issue:
https://github.com/apache/tinkerpop/pull/819
sorry - i didn't see your reply earlier i the week. i think this PR even
without the build changes had problems. the PR branch wasn't building I don't
think (i seem to remember @robertdale brin
Github user leventov commented on the issue:
https://github.com/apache/tinkerpop/pull/819
@spmallette is it considerable?
---
This could be something we try to address some day in TinkerPop 4.x. It
really shouldn't be handled by serialization versions, but it's also not as
simple as a version field. Gremlin is a little different than the standard
query language because the language is bound to the API which is versioned
b