You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2007/10/07 16:15:50 UTC

[jira] Commented: (TAPESTRY-1811) Infer value from id as a prop expression for nested bindings

    [ https://issues.apache.org/jira/browse/TAPESTRY-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532966 ] 

Howard M. Lewis Ship commented on TAPESTRY-1811:
------------------------------------------------

To be honest, I think the code should be clearer that foo.bar is not a valid component id, because of the dot.  An error message such as:

The value 'user.username' is not valid as a component identifier.  Component identifiers may only contain letters and numbers and must start with a letter.

... would not leave any doubt.  Perhaps we should list the unbound parameters?

> 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org