#1005: Allow configuration parameter type casts
-------------------------+--------------------------------------------------
 Reporter:  david        |       Owner:  impl      
     Type:  enhancement  |      Status:  new       
 Priority:  normal       |   Milestone:  1.1       
Component:  config       |     Version:  1.0.0beta7
 Severity:  normal       |    Keywords:            
Has_patch:  0            |  
-------------------------+--------------------------------------------------

Comment(by david):

 Replying to [comment:5 impl]:
 > I thought the idea behind custom parameter names was so we could use
 constants for them (like in Propel/Doctrine configuration). No?

 That was the original idea, but outside of Doctrine and Propel, the use
 case just isn't there I think. Particularily for element names, the syntax
 is just going to spin out of control rather sooner than later. I thought
 about supporting someting like {{{ae:literalize="constant"}}} or similar,
 but that would then only work for values.

 The attractive thing about [wiki:AEPs/AEP-100] is its simplicity; half of
 the functionality is achieved through the standardized {{{xml:space}}}
 attribute.

 We could always add extended functionality later; I think we discussed
 before though that what's specified in the AEP is probably enough for most
 use cases any a reasonable compromise between functionality and
 implementational complexity.

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