[jira] [Reopened] (TINKERPOP-2072) Refactor custom type translation for ScriptTranslators

["stephen mallette (JIRA)" <ji...@apache.org>]

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

stephen mallette reopened TINKERPOP-2072:
-----------------------------------------

> Refactor custom type translation for ScriptTranslators
> ------------------------------------------------------
>
>                 Key: TINKERPOP-2072
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2072
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: groovy
>    Affects Versions: 3.3.4
>            Reporter: stephen mallette
>            Assignee: stephen mallette
>            Priority: Major
>              Labels: breaking
>             Fix For: 3.4.0
>
>
> Refactor the `TypeTranslator` system a bit so that it is better designed for extension rather than the "plugin" style system that exists now. The current method seems to work but it's a bit awkward in that it introduces some circular logic if a custom translator needs to refer back to the default one. In the worst case it means embedding {{GroovyTranslator}} itself in the {{TypeTranslator}}. 
> Anyway, this is a breaking change because it completely alters the old method for handling this. On the plus side, this is a very low-level and internal feature that is only of interest to graph providers so it shouldn't break too much code out there.



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