You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2010/05/14 19:42:43 UTC
[jira] Closed: (TAP5-1035) In places where an invalid key is used
to accessed a named value, Tapestry should report the possible names better
(using HTML lists, rather than a long comma-separated string)
[ https://issues.apache.org/jira/browse/TAP5-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1035.
--------------------------------------
Fix Version/s: 5.2.0
Resolution: Fixed
> In places where an invalid key is used to accessed a named value, Tapestry should report the possible names better (using HTML lists, rather than a long comma-separated string)
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1035
> URL: https://issues.apache.org/jira/browse/TAP5-1035
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.2.0
>
>
> When you use an invalid name, such as a misspelling of a component type, Tapestry is great about listing out the possible names you could have used. However, when there's a lot of those (such as a service id, or a component type, or page name in a large application), the format is hard to parse: long, long, long comma-separated list.
> A better approach would be to use two or three columns of <ul> and <li> elements to present the options in a useful order.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.