You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Barry Books (Created) (JIRA)" <ji...@apache.org> on 2012/02/13 17:26:59 UTC
[jira] [Created] (TAP5-1846) Documentation for Mixins and Informal
Parameters is not correct.
Documentation for Mixins and Informal Parameters is not correct.
----------------------------------------------------------------
Key: TAP5-1846
URL: https://issues.apache.org/jira/browse/TAP5-1846
Project: Tapestry 5
Issue Type: Bug
Components: documentation
Affects Versions: 5.3
Reporter: Barry Books
Priority: Minor
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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-1846) Documentation for Mixins and Informal
Parameters is not correct.
Posted by "Bob Harner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bob Harner closed TAP5-1846.
----------------------------
> Documentation for Mixins and Informal Parameters is not correct.
> ----------------------------------------------------------------
>
> Key: TAP5-1846
> URL: https://issues.apache.org/jira/browse/TAP5-1846
> Project: Tapestry 5
> Issue Type: Bug
> Components: documentation
> Affects Versions: 5.3
> Reporter: Barry Books
> Assignee: Bob Harner
> Priority: Minor
> Labels: documentation
>
> 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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TAP5-1846) Documentation for Mixins and Informal
Parameters is not correct.
Posted by "Bob Harner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bob Harner resolved TAP5-1846.
------------------------------
Resolution: Fixed
Assignee: Bob Harner
Updated http://tapestry.apache.org/component-mixins.html with the suggested wording -- thanks to Barry Books
> Documentation for Mixins and Informal Parameters is not correct.
> ----------------------------------------------------------------
>
> Key: TAP5-1846
> URL: https://issues.apache.org/jira/browse/TAP5-1846
> Project: Tapestry 5
> Issue Type: Bug
> Components: documentation
> Affects Versions: 5.3
> Reporter: Barry Books
> Assignee: Bob Harner
> Priority: Minor
> Labels: documentation
>
> 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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-1846) Documentation for Mixins and Informal
Parameters is not correct.
Posted by "Bob Harner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bob Harner closed TAP5-1846.
----------------------------
> Documentation for Mixins and Informal Parameters is not correct.
> ----------------------------------------------------------------
>
> Key: TAP5-1846
> URL: https://issues.apache.org/jira/browse/TAP5-1846
> Project: Tapestry 5
> Issue Type: Bug
> Components: documentation
> Affects Versions: 5.3
> Reporter: Barry Books
> Assignee: Bob Harner
> Priority: Minor
> Labels: documentation
>
> 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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TAP5-1846) Documentation for Mixins and Informal
Parameters is not correct.
Posted by "Bob Harner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bob Harner resolved TAP5-1846.
------------------------------
Resolution: Fixed
Assignee: Bob Harner
Updated http://tapestry.apache.org/component-mixins.html with the suggested wording -- thanks to Barry Books
> Documentation for Mixins and Informal Parameters is not correct.
> ----------------------------------------------------------------
>
> Key: TAP5-1846
> URL: https://issues.apache.org/jira/browse/TAP5-1846
> Project: Tapestry 5
> Issue Type: Bug
> Components: documentation
> Affects Versions: 5.3
> Reporter: Barry Books
> Assignee: Bob Harner
> Priority: Minor
> Labels: documentation
>
> 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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira