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

        Hide
        Norbert Sándor added a comment -

        That's not the same because I have to copy-paste the original .jwc files and monitor the changes in them... forever

        Show
        Norbert Sándor added a comment - That's not the same because I have to copy-paste the original .jwc files and monitor the changes in them... forever
        Hide
        Andreas Andreou added a comment -

        I don't see this happening - even though i dont exactly remember the original reasoning for the naming.

        You can always have your own empty If class, like

        public abstract class If extends IfBean {}

        and use that in your own project.

        Show
        Andreas Andreou added a comment - I don't see this happening - even though i dont exactly remember the original reasoning for the naming. You can always have your own empty If class, like public abstract class If extends IfBean {} and use that in your own project.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development