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 2018/09/19 20:30:00 UTC
[jira] [Created] (TINKERPOP-2040) Improve flexibility of
GroovyTranslator to handle custom types
stephen mallette created TINKERPOP-2040:
-------------------------------------------
Summary: Improve flexibility of GroovyTranslator to handle custom types
Key: TINKERPOP-2040
URL: https://issues.apache.org/jira/browse/TINKERPOP-2040
Project: TinkerPop
Issue Type: Improvement
Components: groovy
Affects Versions: 3.2.9
Reporter: stephen mallette
Assignee: stephen mallette
{{GroovyTranslator}} only handles a set body of types. If for some reason however an object is passed to it in the traversal that it doesn't know how to properly handle you could get an invalid groovy string. It would be good if it could not only handle new types but also override existing ones (not sure why an override would be needed, but does't seem like a wrong thing to allow).
This change is slightly bigger than {{GroovyTranslator}} though because however the override will take place it will need to be possible to use it within the script engine somehow and right now it is initialized statically.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)