Uploaded image for project: 'TinkerPop'
  1. TinkerPop
  2. TINKERPOP-2040

Improve flexibility of GroovyTranslator to handle custom types

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 3.2.9
    • Fix Version/s: 3.4.0, 3.3.4, 3.2.10
    • Component/s: groovy
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              spmallette Stephen Mallette
              Reporter:
              spmallette Stephen Mallette

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment