[jira] [Commented] (TINKERPOP3-850) Reduce Graph.addVertex overload ambiguity

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

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

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

This is okay for me. However, its an API update and requires {{@Deprecation}}. However, we can have default implementation for the for the first method.

I'm going to pass this to [~spmallette] for review to see what he thinks as I think he has a deeper understanding of the rippling effects.

> Reduce Graph.addVertex overload ambiguity
> -----------------------------------------
>
>                 Key: TINKERPOP3-850
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-850
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.0.1-incubating
>            Reporter: Matt Frantz
>            Assignee: Marko A. Rodriguez
>             Fix For: 3.0.2-incubating
>
>
> Create the following overloads:
> {noformat}
> Vertex addVertex();
> Vertex addVertex(String label);
> Vertex addVertex(Object key, Object value, Object...keyValues);
> {noformat}
> This would avoid the 1-arg overload, since there is only one 1-arg variant.  It also makes the key/value structure more obvious.
> BTW, the JavaDoc now says "...the odd numbered arguments are String property keys," so if we actually allow other types, that doc should be fixed.
> Motivated by this dicussion: https://groups.google.com/d/msgid/gremlin-users/eb2a451a-af66-48a1-989c-8021473647fc%40googlegroups.com



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