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.0.0
Reporter: Howard M. Lewis Ship
Priority: Minor
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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
