#793: Assigning of "inner" content to slots should be configurable
--------------------+-------------------------------------------------------
 Reporter:  david   |        Owner:  david 
     Type:  task    |       Status:  new   
 Priority:  normal  |    Milestone:  0.11.3
Component:  filter  |      Version:        
 Severity:  minor   |   Resolution:        
 Keywords:          |    Has_patch:  0     
--------------------+-------------------------------------------------------
Changes (by david):

  * summary:  Do not put inner content into the slots array by default =>
              Assigning of "inner" content to slots should be
              configurable
  * milestone:  1.0 => 0.11.3

Old description:

> Since there is {{{$inner}}} with the current rendering result available
> in templates, it makes not much sense to also have this previous layer's
> output in the {{{$slots}}} array, it's just legacy.
>
> We need to introduce a configuration parameter for the execution filter
> that enables this functionality and defaults to off.

New description:

 Since there is {{{$inner}}} with the current rendering result available in
 templates, it makes not much sense to also have this previous layer's
 output in the {{{$slots}}} array, it's just legacy.

 We need to introduce a configuration parameter for the execution filter
 that enables this functionality (and defaults to on for 0.11, off for 1.0,
 see #794)

-- 
Ticket URL: <http://trac.agavi.org/ticket/793#comment:1>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5


_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets

Reply via email to