Weekly todo activity, Apr 17 to Apr 24
| Newsgroups | gmane.comp.web.mason.devel |
|---|---|
| Message-ID | <[email protected]> |
Weekly todo activity, Apr 17 to Apr 24
New task #580: Simplify base_comp exception logic
Right now the base_comp always changes to a called component
except when:
* a component call is made to a component object
* a component call is made to SELF:x or PARENT:x or
REQUEST:x
* a component call is made to a subcomponent (<%def>)
I would like to eliminate the component object and REQUEST:
exceptions.
The component object exception is completely arbitrary, and
I've seen several folks get bitten by this when they
innocuously change from using a component path to a
component object for performance or other legitimate
reasons.
The REQUEST: exception is inconsistent with other method
calls; the base_comp should change to the request component
in this case.
This would mean base_comp would change to the called
component except when:
* a component call is made to SELF:x or PARENT:x
* a component call is made to a subcomponent (<%def>)
which are both perfectly reasonable exceptions. If you want
to manually keep the same base_comp, you can pass
{base_comp=>$m->base_comp} as a modifier.
This is a backward incompatibility, which is why it needs to
be done in a major version.
Mon Apr 18 Jonathan Swartz created task
Jonathan Swartz set owner to jswartz
Jonathan Swartz changed version_goal from 1.3x to 1.29_02
http://www.masonhq.com/docs/todo/access.html?id=580
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click