[
https://issues.apache.org/jira/browse/TAPESTRY-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-1811.
------------------------------------------
Resolution: Won't Fix
Assignee: Howard M. Lewis Ship
There's a conflict between your proposed support for a dot (".") in the
component id, and the use of dot as a separator in nested ids, such as those
that appear in URLs. At this time, I do not wish to change the use of dots in
action URLs which makes this bug relatively unfixable (well, we could layer a
kludge on it, like translating '.' to '@' when building a URL).
I've always seen the default parameter binding from the component id as a
bonus, not a requirement. This bug would promote that bonus up to a pretty
hard-core requirement.
> 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
> Assignee: Howard M. Lewis Ship
> 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]
