[jira] Updated: (TAPESTRY-1340) Long lists in the exception report would be easier to read in unordered list format

["Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>]

     [ https://issues.apache.org/jira/browse/TAPESTRY-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAPESTRY-1340:
-------------------------------------------

    Priority: Minor  (was: Major)

> Long lists in the exception report would be easier to read in unordered list format
> -----------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1340
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1340
>             Project: Tapestry
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.0
>            Reporter: 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.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org