[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)

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.2.0
• Fix Version/s: 5.2.0
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 27/Feb/10 02:06
• Updated: 14/May/10 17:40
• Resolved: 14/May/10 17:40

Description

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.