[jira] [Updated] (TINKERPOP3-800) [Proposal] Domain/Range checking during traversal construction.

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

     [ https://issues.apache.org/jira/browse/TINKERPOP3-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marko A. Rodriguez updated TINKERPOP3-800:
------------------------------------------
    Fix Version/s: 3.2.0-incubating

> [Proposal] Domain/Range checking during traversal construction.
> ---------------------------------------------------------------
>
>                 Key: TINKERPOP3-800
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-800
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.0.2-incubating
>            Reporter: Marko A. Rodriguez
>            Assignee: Marko A. Rodriguez
>              Labels: breaking
>             Fix For: 3.2.0-incubating
>
>
> I think we should add two new methods to {{Step}}.
> {code}
> Step.getDomain() -> Class
> Step.getRange() -> Class
> {code}
> Now, when someone does:
> {code}
> g.V().out()
> {code}
> {{GraphStep}} will report that its range is {{Vertex.class}}. {{VertexStep}} will report its domain to be {{Vertex.class}}. Good. No typing issues. However, when you do this:
> {code}
> g.E().out()
> {code}
> {{GraphStep}} will report that its range is {{Edge.class}}. {{VertexStep}} will report its domain to be {{Vertex.class}} --- {{IllegalArgumentException: "The provided traversal has an illegal function composition."}}.
> Why is this good -- much better than getting random {{ClassCastExceptions}} at execution time.



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