tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Riedel (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TAP5-843) Allow nested symbol definitions
Date Thu, 08 Oct 2009 17:46:31 GMT

    [ https://issues.apache.org/jira/browse/TAP5-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763590#action_12763590
] 

Christian Riedel commented on TAP5-843:
---------------------------------------

Does that issue also cover expansions? A nested expansion like that would save lots of code:
${asset:context:images/${someObject.imageName}}

> 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.0.0
>            Reporter: Howard M. Lewis Ship
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message