[
https://issues.apache.org/jira/browse/TAPESTRY-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534719
]
Nick Westgate commented on TAPESTRY-1830:
-----------------------------------------
Howard has suggested we use the component's own parameters which will be made
public.
When the expression language (i.e. not the current version of "prop") can
access the component it will suffice for this use case.
Cheers,
Nick.
> allow local value and index parameters (i.e. not page class variables) in
> loop, count ... components
> ----------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1830
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1830
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: M. H. Shamsi
> Fix For: 5.0.6
>
>
> index and value parameter in loop (and all components like it) often used
> just in page templates and there is no need to access or change them in page
> class.
> sharing this parameters to use directly in page templates, may help
> developers to write most cleaner page classes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
