[
https://issues.apache.org/jira/browse/TAPESTRY-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629327#action_12629327
]
Howard M. Lewis Ship commented on TAPESTRY-1340:
------------------------------------------------
I've been thinking that rather than force the output via regexps (which really
is not viable), including a "detail" property on TapestryException would be
useful. This could be a string, list, map or other object, and would be
rendered as part of the exception page.
> 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
> Fix For: 5.1
>
>
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
