#561: [PATCH] Slot Population Filter
-------------------------+--------------------------------------------------
 Reporter:  ross         |        Owner:  david    
     Type:  enhancement  |       Status:  new      
 Priority:  normal       |    Milestone:  0.11     
Component:  filter       |      Version:  0.11.0RC5
 Severity:  normal       |   Resolution:           
 Keywords:               |  
-------------------------+--------------------------------------------------
Old description:

> == SPF ==
>
> This '''''action'' filter''' automagically allows Slots to store their
> state, so that if they error they can be returned to the action from
> whence they came.
>
> It has a few options for controlling the filter - so it can be used in
> multiple circumstances.
>
>  * '''disabled''' - Toggle the SPF and allow slots to determine how to
> handle their own errors.
>  * '''maintain_slot_context''' - Attempts to maintain the slot context
> even if there have been no validation errors (untested and may not be
> useful)
>  * '''slots_to_overwrite''' - slots information to be overridden if needs
> be. (i.e. it will be over write the slots to be actioned array)
>  * '''slots_to_ignore''' - slots information that will be ignored. (i.e.
> they will be removed from the slots to be actioned array)
>  * '''slots_to_add''' - An array of slot, that can be added for some
> reason (i.e. added to the slots to be actioned array)
>  * '''slot_data_to_remove''' - An array of keys to be removed from the
> request data holder. i.e. you have some PDO data that wont be serialised
>
> All these can be modified in any view by setting an attribute to the
> 'org.agavi.filter.!SlotPopulationFilter'
>
> ie.
>
> {{{
> $this->context->getRequest()->setAttribute('disabled', false,
> 'org.agavi.filter.SlotPopulationFilter');
> }}}
>
> == Dependencies ==
>  * You will need to apply these two patches [#560] and [#303] (the SPF
> FPF Patch)

New description:

 == SPF ==

 This '''''action'' filter''' automagically allows Slots to store their
 state, so that if they error they can be returned to the action from
 whence they came.

 It has a few options for controlling the filter - so it can be used in
 multiple circumstances.

  * '''disabled''' - Toggle the SPF and allow slots to determine how to
 handle their own errors.
  * '''maintain_slot_context''' - Attempts to maintain the slot context
 even if there have been no validation errors (untested and may not be
 useful)
  * '''slots_to_overwrite''' - slots information to be overridden if needs
 be. (i.e. it will be over write the slots to be actioned array)
  * '''slots_to_ignore''' - slots information that will be ignored. (i.e.
 they will be removed from the slots to be actioned array)
  * '''slots_to_add''' - An array of slot, that can be added for some
 reason (i.e. added to the slots to be actioned array)
  * '''slot_data_to_remove''' - An array of keys to be removed from the
 request data holder. i.e. you have some PDO data that wont be serialised

 All these can be modified in any view by setting an attribute to the
 'org.agavi.filter.!SlotPopulationFilter'

 ie.

 {{{
 $this->context->getRequest()->setAttribute('disabled', false,
 'org.agavi.filter.SlotPopulationFilter');
 }}}

 == Dependencies ==
  * You will need agavi version -r 2065 or above and apply  the SPF FPF
 Patch ([#303])

-- 
Ticket URL: <http://trac.agavi.org/ticket/561#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