You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2014/05/27 09:20:06 UTC

[jira] [Updated] (TAP5-864) ComponentResources should expose an API that describes sub-components & formal/informal parameters (to be used as a diagnostic tool)

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

Jochen Kemnade updated TAP5-864:
--------------------------------

    Labels: bulk-close-candidate  (was: )

This issue has been last updated about 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent development preview of Tapestry (5.4-beta-6, which is available from Maven Central), please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the dev@tapestry.apache.org mailing list first.


> ComponentResources should expose an API that describes sub-components & formal/informal parameters (to be used as a diagnostic tool)
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-864
>                 URL: https://issues.apache.org/jira/browse/TAP5-864
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.2
>            Reporter: Howard M. Lewis Ship
>            Priority: Minor
>              Labels: bulk-close-candidate
>
> T3 had the inspector ... and I've built on-offs in T4 that identifies the # of components on a page.  A ComponentStats interface could identify the immediate components (by id), the type (and count) of each components directly within a component, as well as a roll up. This would make it possible (given a UI) to drill-down and see which pages and which components contribute to the Uber-component anti-pattern.



--
This message was sent by Atlassian JIRA
(v6.2#6252)