[
https://issues.apache.org/jira/browse/TAP5-843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade updated TAP5-843:
--------------------------------
Labels: bulk-close-candidate (was: )
This issue has been last updated about 1.5 years ago, has no assignee, affects
an old version of Tapestry that is not actively developed anymore, and is
therefore prone to be bulk-closed in the near future.
If the issue still persists with the most recent development preview of
Tapestry (5.4-beta-6, which is available from Maven Central), please update it
as soon as possible. In the case of a feature request, please discuss it with
the Tapestry developer community on the [email protected] mailing list
first.
> Allow nested symbol definitions
> -------------------------------
>
> Key: TAP5-843
> URL: https://issues.apache.org/jira/browse/TAP5-843
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-ioc
> Affects Versions: 5.2
> Reporter: Howard M. Lewis Ship
> Labels: bulk-close-candidate
>
> It would be nice if a Symbol's definition could be nested, i.e.
> ${foo.${bar}}
> This would evaluate ${bar} forming a new symbol name prefixed by 'foo', which
> would then itself be evaluated.
> Boy this is going to complicate the circular logic detection code!
--
This message was sent by Atlassian JIRA
(v6.2#6252)
