Tapestry
  1. Tapestry
  2. TAPESTRY-1179

practical component class naming for For, If and Else

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Affects Version/s: 4.1.1
    • Fix Version/s: 4.1.2
    • Component/s: Framework
    • Labels:
      None

      Description

      Because @Component's type is not required anymore, it would be practical to rename ForBean, IfBean and ElseBean to For, If, Else accordingly.

      Regards,
      Norbi

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Norbert Sándor
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development