[
https://issues.apache.org/jira/browse/TAP5-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721699#action_12721699
]
Hugo Palma commented on TAP5-742:
---------------------------------
I think enabling component debugging on a request-by-request basis would be
really helpful.
What about if the parameter was there but Tapestry would only actually use it's
value if tapestry.prodution-mode was false ? Wouldn't that provide both ease of
use and security ?
> 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.
