[
https://issues.apache.org/jira/browse/TAP5-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973261#action_12973261
]
Dan Adams commented on TAP5-1378:
---------------------------------
What would the advantages of a local macro be? Are there things you could do
with lifecycles or mixins or something that you can't do here that would be
useful? I really like the idea of this being at the component level and not
having to extend the template spec.
btw, I'm going to investigate if there is a way to support generics or extended
prop expressions beyond what var: supports for this. Although, I've been using
an implementation of this for months and months and never needed it. You can
always make it a component if you really need to, but the simple support using
render variables is really nice to have as an option.
> Allow Delegate component to be used for creating in-template components
> -----------------------------------------------------------------------
>
> Key: TAP5-1378
> URL: https://issues.apache.org/jira/browse/TAP5-1378
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.2.4
> Reporter: Dan Adams
>
> Allow the delegate component to accept informal parameters and pass those to
> the block being rendered as render variables. This allows creating a
> component-with-a-component extremely easily using a block. I've got an
> implementation of this that we've used successfully for a while that I can
> contribute or use as as base.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
