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

ASF GitHub Bot commented on GEODE-728:
--------------------------------------

GitHub user dalyssakim opened a pull request:

    https://github.com/apache/geode/pull/457

    GEODE-728 : Rename Execution.withArgs to Execution.setArguments

     * created setArguments
     * deprecated withArgs
     * implemented setArguments of all Execution implementations in Geode 
project
     * replaced all of withArgs with setArguments

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/dalyssakim/geode feature/GEODE-728

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/geode/pull/457.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 #457
    
----
commit 8dc7cadb664c19df8ddea17f01e697472ec839cd
Author: Alyssa Kim <micro9...@gmail.com>
Date:   2017-04-16T00:48:00Z

    GEODE-728 : Rename Execution.withArgs to Execution.setArguments
     * created setArguments
     * deprecated withArgs
     * implemented setArguments of all Execution implementations in Geode 
project
     * replaced all of withArgs with setArguments

----


> Rename Execution.withArgs to Execution.setArguments
> ---------------------------------------------------
>
>                 Key: GEODE-728
>                 URL: https://issues.apache.org/jira/browse/GEODE-728
>             Project: Geode
>          Issue Type: Improvement
>          Components: docs, functions
>            Reporter: Dan Smith
>            Assignee: Alyssa Kim
>
> FunctionContext has a getArguments method. withArgs should be renamed to 
> match.
> See this discussion on the mailing list.
> http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201512.mbox/browser



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to