You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Stephen Mallette (Jira)" <ji...@apache.org> on 2020/11/13 19:59:00 UTC

[jira] [Closed] (TINKERPOP-2461) Align CoreImports with GroovyTranslator

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

Stephen Mallette closed TINKERPOP-2461.
---------------------------------------
    Fix Version/s: 3.4.9
                   3.5.0
       Resolution: Done

> Align CoreImports with GroovyTranslator
> ---------------------------------------
>
>                 Key: TINKERPOP-2461
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2461
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: translator
>    Affects Versions: 3.4.8
>            Reporter: Stephen Mallette
>            Assignee: Stephen Mallette
>            Priority: Major
>             Fix For: 3.5.0, 3.4.9
>
>
> {{GroovyTranslator}} makes some arbitrary choices about including package names in its output.  A fair presumption should be that types common to Gremlin IO should not need the specificity of the package name (e.g. {{UUID}}). I think it would be smart if the {{DefaultTypeTranslator}} used {{ImportCustomizer}} instances to control which objects needed package specification and which did not. {{ImportCustomizer}} is the same interface handed to the {{GremlinGroovyScriptEngine}} and therefore seems to be the ideal vehicle to help control {{GroovyTranslator}} output.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)