Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.5 beta2
    • Fix Version/s: 1.6
    • Component/s: Engine
    • Labels:
      None

      Description

      On a separate issue (VELOCITY-504) we came up with the idea of a new directive, #evaluate. Basically, it would act just like Velocity.evaluate().

      Users are always asking for this capability (internal evaluation). Usually we tell them to "use a tool". Instead, we should just put in a simple directive that would evaluate a VTL string using the current context.

      Incidentally, this should be the current local context, e.g. if inside a macro or a foreach loop (or worse, both) it should use that context. See VELOCITY-504 for why this is needed.

        Issue Links

          Activity

          Will Glass-Husain created issue -
          Will Glass-Husain made changes -
          Field Original Value New Value
          Link This issue relates to VELOCITY-504 [ VELOCITY-504 ]
          Will Glass-Husain made changes -
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Resolved [ 5 ]
          Mark Thomas made changes -
          Workflow jira [ 12393457 ] Default workflow, editable Closed status [ 12551481 ]
          Mark Thomas made changes -
          Workflow Default workflow, editable Closed status [ 12551481 ] jira [ 12552230 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              Will Glass-Husain
            • Votes:
              2 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development