Tapestry
  1. Tapestry
  2. TAPESTRY-1485

Remove the Any component --- not necessary because of expansions in attributes

    Details

    • Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0
    • Fix Version/s: 5.0.5
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      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).

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Howard M. Lewis Ship
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development