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)" <ta...@jakarta.apache.org> on 2007/03/10 04:00:09 UTC
[jira] Created: (TAPESTRY-1340) Long lists in the exception report
would be easier to read in unordered list format
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
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
[jira] Updated: (TAPESTRY-1340) Long lists in the exception report
would be easier to read in unordered list format
Posted by "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
[jira] Updated: (TAP5-77) Long lists in the exception report would
be easier to read in unordered list format
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-77:
-------------------------------------
Assignee: (was: Howard M. Lewis Ship)
Affects Version/s: (was: 5.0.15)
5.1.0.0
> 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
> 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
[jira] Assigned: (TAP5-77) Long lists in the exception report would
be easier to read in unordered list format
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-77:
----------------------------------------
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.0.15
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-1340) Long lists in the exception
report would be easier to read in unordered list format
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAP5-77) Long lists in the exception report would
be easier to read in unordered list format
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-77:
-------------------------------------
Issue Type: Improvement (was: Bug)
> 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.0.15
> 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
[jira] Updated: (TAPESTRY-1340) Long lists in the exception report
would be easier to read in unordered list format
Posted by "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:
-------------------------------------------
Fix Version/s: 5.1
> 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org