You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Joost Schouten (JIRA)" <ji...@apache.org> on 2009/11/16 09:42:39 UTC
[jira] Commented: (TAP5-742) Add optional component tracing
comments to rendered output
[ https://issues.apache.org/jira/browse/TAP5-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778261#action_12778261 ]
Joost Schouten commented on TAP5-742:
-------------------------------------
+1 Unit testing is where is comes in handy. With the addition of the component class to te comment It will allow you to do things like assertComponentOnPage(MyComponent.class).
> Add optional component tracing comments to rendered output
> ----------------------------------------------------------
>
> Key: TAP5-742
> URL: https://issues.apache.org/jira/browse/TAP5-742
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.1.0.5
> Reporter: Howard M. Lewis Ship
> Priority: Minor
>
> In complex pages, it can be hard to work backwards from a bit of output HTML in the browser, back to the component that originated the markup.
> A special mode could be enabled where components would render a comment before and after rendering:
> <!-- BEGIN: Index:layout.pagelink -->
> <a href="dashboard">Dashboard</a>
> <!-- END: Index:layout.pagelink -->
> This would bloat and clutter the application (a lot!) but would be useful, on occasion. One possibility would be a special query parameter to enable this on a request-by-request basis, i.e., ?t:component-trace=true
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.