[
https://issues.apache.org/jira/browse/TINKERPOP3-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14484357#comment-14484357
]
ASF GitHub Bot commented on TINKERPOP3-615:
-------------------------------------------
GitHub user mhfrantz opened a pull request:
https://github.com/apache/incubator-tinkerpop/pull/49
TINKERPOP3-615 cap(String, String...) to require at least one side effect
key
https://issues.apache.org/jira/browse/TINKERPOP3-615
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/RedSeal-co/incubator-tinkerpop TINKERPOP3-615
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-tinkerpop/pull/49.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #49
----
commit 116cdaf27c9bd04a6df26a818ff92c4e85b2c6ba
Author: mfrantz <[email protected]>
Date: 2015-04-07T23:37:50Z
TINKERPOP3-615 cap(String, String...) to require at least one side effect
key
----
> cap(String, String...)
> ----------------------
>
> Key: TINKERPOP3-615
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-615
> Project: TinkerPop 3
> Issue Type: Bug
> Reporter: Matt Frantz
> Priority: Minor
>
> Since cap (SideEffectCapStep) raises an exception if no keys are provided, we
> should just let the compiler do the work by changing the signature. This
> should set the precedent for "one or more varargs".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
