[
https://issues.apache.org/jira/browse/FREEMARKER-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17349939#comment-17349939
]
Dániel Dékány commented on FREEMARKER-112:
------------------------------------------
[[email protected]] What's up with this?
> Inspect Freimarken Variables in Template for e.g. Testing
> ---------------------------------------------------------
>
> Key: FREEMARKER-112
> URL: https://issues.apache.org/jira/browse/FREEMARKER-112
> Project: Apache Freemarker
> Issue Type: Wish
> Components: engine
> Affects Versions: 2.3.28
> Environment: ALL
> Reporter: Yuna Morgenstern
> Priority: Critical
> Labels: easyfix
> Fix For: 2.3.29
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> h5. Story
> As tester and backend tool developer
> we wish to inspect variables of a template
> so that we can test template structure before rendering, while testing and
> can present internally a gui tool which will show all variables, default
> values and all that stuff
> h5. Description
> FreeMarker already scans the template, so why not giving access to the parsed
> elements? It would be sad if we have to implement the same parsing logic as
> FreeMarker already does.
> h5. Acceptance criteria
> * parsed elements like e.g. freemarker.core.* can be accessed by e.g.
> (freemarker.coreTemplate.getRootTreeNode().getVariables() )
> * Variables are having types like, optional, required, predefined/constant,...
> * Variables are having default parameter which can be reached by another
> getter
> h5. Links example
> https://stackoverflow.com/questions/1919189/how-can-i-introspect-a-freemarker-template-to-find-out-what-variables-it-uses
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
