You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@freemarker.apache.org by "Daniel Dekany (JIRA)" <ji...@apache.org> on 2017/07/05 09:01:00 UTC
[jira] [Closed] (FREEMARKER-60) Document interaction between lazy
import and #global
[ https://issues.apache.org/jira/browse/FREEMARKER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Dekany closed FREEMARKER-60.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.3.27-incubating
As the subject (to document this thing) was resolved, I close this issue. We can discuss the other ideas/problems further of course (open a separate issue or on the mailing list).
> Document interaction between lazy import and #global
> ----------------------------------------------------
>
> Key: FREEMARKER-60
> URL: https://issues.apache.org/jira/browse/FREEMARKER-60
> Project: Apache Freemarker
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 2.3.26-incubating
> Reporter: Jasper Rosenberg
> Priority: Trivial
> Fix For: 2.3.27-incubating
>
>
> If I am understanding what is going on correctly, it appears that when you turn on lazy imports, #global variables defined in that file will not be defined unless something else first accesses the imported file's namespace. This is a bit of a weird case so it might just be worth documenting.
> Alternatively, you could say that if you have #global variables defined in a file it disqualifies it from being lazily imported.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)