You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2018/06/20 10:28:00 UTC
[jira] [Closed] (TINKERPOP-1988) minor error in documentation
[ https://issues.apache.org/jira/browse/TINKERPOP-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stephen mallette closed TINKERPOP-1988.
---------------------------------------
Resolution: Fixed
ha - 2 decades of writing code and every once in a while simple and/or/not expressions still get me. you're right it should be when the traversal argument returns an object - not the opposite.
https://github.com/apache/tinkerpop/commit/7c7dddb72e240cb3167d88aecd4de365589a1f2f
> minor error in documentation
> ----------------------------
>
> Key: TINKERPOP-1988
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1988
> Project: TinkerPop
> Issue Type: Bug
> Components: documentation
> Affects Versions: 3.3.3
> Reporter: Sim Bamford
> Assignee: stephen mallette
> Priority: Trivial
> Fix For: 3.4.0, 3.3.4, 3.2.10
>
>
> Not sure where to put a problem with the documentation(?) The page:
> [http://tinkerpop.apache.org/docs/current/reference/]
> States:
> "TheĀ {{not()}}-step (*filter*) removes objects from the traversal stream when the traversal provided as an argument does not return any objects."
> Isn't that wrong? surely the traversal is removed if the argument does return objects?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)