Remove the Any component --- not necessary because of expansions in attributes
------------------------------------------------------------------------------
Key: TAPESTRY-1485
URL: https://issues.apache.org/jira/browse/TAPESTRY-1485
Project: Tapestry
Issue Type: Task
Components: tapestry-core
Affects Versions: 5.0
Reporter: Howard M. Lewis Ship
The Any component (and the logic that allows a component with an id but not
type to be an Any component) is no longer necessary.
Because of TAPESTRY-1466, ordinary elements can now have dynamic attributes via
expansions (in those attributes).
Removing the Any component will remove an odd ambiguity, and allow us to
identify components where the developer has accidentally forgotten to specify
the type (either with t:type or via the @Component annotation).
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]