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)" <ji...@apache.org> on 2009/02/26 20:37:02 UTC
[jira] Closed: (TAP5-77) Long lists in the exception report would
be easier to read in unordered list format
[ https://issues.apache.org/jira/browse/TAP5-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-77.
------------------------------------
Resolution: Won't Fix
Assignee: Howard M. Lewis Ship
> Long lists in the exception report would be easier to read in unordered list format
> -----------------------------------------------------------------------------------
>
> Key: TAP5-77
> URL: https://issues.apache.org/jira/browse/TAP5-77
> Project: Tapestry 5
> Issue Type: Improvement
> Affects Versions: 5.1.0.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> There's a number of places where an exception message ends with a comma separated list of values (such as a list of pages, or a list of components). It would be very nice if this could be intercepted in some way and reformatted for readability, i.e.:
> Available components: Foo, Bar, Baz.
> would become:
> Available components:<ul><li>Foo</li><li>Bar</li><li>Baz</li></ul>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.