[
https://issues.apache.org/jira/browse/TAPESTRY-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532986
]
Nick Westgate commented on TAPESTRY-1811:
-----------------------------------------
Why restrict identifiers so? Actually, the fact that dots are allowed in id's
complicates the suggestion, I suppose.
The exception for the "user.username" case lists unbound required parameters
but gives no hint of the automatic value search/failure:
"Parameter(s) translate, value are required for
org.apache.tapestry.corelib.components.TextField, but have not been bound."
Cheers,
Nick.
> Infer value from id as a prop expression for nested bindings
> ------------------------------------------------------------
>
> Key: TAPESTRY-1811
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1811
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: Nick Westgate
> Priority: Minor
>
> When no value is given, id is used to check for a property. This works:
> <t:textfield t:id="username" t:validate="required"/>
> This was posted to the user list:
> <t:textfield t:id="user.username" t:validate="required"/>
> It would be nice if the given id were treated as a prop expression for the
> value binding.
> Cheers,
> Nick.
--
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]
