Tapestry 5
  1. Tapestry 5
  2. TAP5-285

Components such as ActionLink and EventLink should require that there be *some* event handler for their triggered events

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.15
    • Fix Version/s: 5.0.16
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      If an the event URL for an ActionLink or EventLink is triggered, but there's no event handler for the server-side event, that should be an error: what's the point of having such a link if there's no behavior on the server side to go with it?

      Other components that generate optional events (such as Form) should be forgiving about missing event handlers; they are optional not truly missing.

        Activity

        Howard M. Lewis Ship made changes -
        Field Original Value New Value
        Fix Version/s 5.0.16 [ 12313427 ]
        Status Open [ 1 ] Closed [ 6 ]
        Resolution Fixed [ 1 ]
        Assignee Howard M. Lewis Ship [ hlship ]
        Howard M. Lewis Ship created issue -

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development