Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-1846

Documentation for Mixins and Informal Parameters is not correct.

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 5.3
    • Fix Version/s: None
    • Component/s: documentation
    • Labels:

      Description

      The current documentation states:

      If the component and a Mixin both define a parameter with the same name, then the component wins: the component's parameter will be bound, and the Mixin's parameter will be unbound.

      Alternately, you may prefix the name of the parameter with the unqualified name of the Mixin class

      It's not clear from this statement what happens to unqualified informal parameters when the component and Mixins support informal parameters but it appears the current implementation will never assign any informal parameters to a component if you add a Mixin that supports informal parameters. Please add something like the following to the documentation:

      In the case of informal parameters without a qualifier the Mixin that supports informal parameters will receive the all the unqualified informal parameters. If more than one Mixin supports informal parameters the results are undefined.

      Thanks

        Attachments

          Activity

            People

            • Assignee:
              bobharner Bob Harner
              Reporter:
              trsvax Barry Books
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: