You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Nick Westgate (JIRA)" <de...@tapestry.apache.org> on 2007/10/07 07:43:50 UTC
[jira] Created: (TAPESTRY-1811) Infer value from id as a prop
expression for nested bindings
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
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
[jira] Closed: (TAPESTRY-1811) Infer value from id as a prop
expression for nested bindings
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-1811) Infer value from id as a prop
expression for nested bindings
Posted by "Nick Westgate (JIRA)" <de...@tapestry.apache.org>.
[ 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-1811) Infer value from id as a prop
expression for nested bindings
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ 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
[jira] Updated: (TAPESTRY-1811) Infer value from id as a prop
expression for nested bindings
Posted by "Nick Westgate (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Westgate updated TAPESTRY-1811:
------------------------------------
Priority: Minor (was: Major)
> 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