tinkerpop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TINKERPOP-1831) Refactor EventStrategy
Date Fri, 08 Jun 2018 19:58:00 GMT

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

ASF GitHub Bot commented on TINKERPOP-1831:
-------------------------------------------

Github user dkuppitz commented on the issue:

    https://github.com/apache/tinkerpop/pull/872
  
    VOTE: +1


> Refactor EventStrategy 
> -----------------------
>
>                 Key: TINKERPOP-1831
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1831
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: structure
>    Affects Versions: 3.2.6
>            Reporter: stephen mallette
>            Assignee: stephen mallette
>            Priority: Minor
>              Labels: breaking
>             Fix For: 3.4.0
>
>
> {{EventStrategy}} has a few issues that could be smoothed out, but not without an allowance
for breaking change in the API:
> * For the creation of new properties, an empty detached property is created to represent
it - now that detachment is configurable, that doesn't always make sense. For example, if
you configured for reference detachment then you would probably want a {{ReferenceProperty}}
instead. Not sure how this should be resolved, but it probably needs a change to the eventing
API itself
> * Detachment is configured a bit strangely with the use of {{null}} and passing classes
for the appropriate detachment factories....would be nicer to have an interface to represent
this stuff.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message