[jira] [Commented] (TINKERPOP3-862) Add a TraversalSourceStrategy that provides "locked" values.

["Marko A. Rodriguez (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TINKERPOP3-862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979095#comment-14979095 ] 

Marko A. Rodriguez commented on TINKERPOP3-862:
-----------------------------------------------

This is a nice idea, but not crucial. Removing it from the 3.1.0 release.

> Add a TraversalSourceStrategy that provides "locked" values.
> ------------------------------------------------------------
>
>                 Key: TINKERPOP3-862
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-862
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.0.1-incubating
>            Reporter: Marko A. Rodriguez
>            Assignee: Marko A. Rodriguez
>
> We have:
> {code}
> withSack()
> withPath()
> withSideEffect()
> {code}
> This can get tedious to continuously type. If a user will always have something like {{withSack(1.0,sum)}}, then perhaps they can do this:
> {code}
> gremlin> g = graph.traversal(GraphTraversalSource.with(TraversalSourceStrategy.build().withSack(1.0,sum).create()))
> gremlin> g.V().sack() 
> ==>1.0
> ==>1.0
> ==>1.0
> ==>1.0
> ==>1.0
> ==>1.0
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)