Hi, > Fixing this "numeric vs. string key" bug (by perhaps utilizing > (array_merge_recursive ?) will not solve the original problem because > you still won't be able to completely override the "standard_helpers" > setting, you'll just be able to append to it. The full solution would > involve distinguishing between "user value" arrays and "containment > hierarchy" arrays...
I don't think that's the perfect solution either. One nice thing of the whole configuration cascade is that you can define things you need everywhere globally and extend them locally. When always redefining "user value" arrays this feature would be lost. Maybe some "magic values" like "-*" that can remove array items would be a better idea. It is already done for HTML assets: http://www.symfony-project.com/book/trunk/07-Inside-the-View-Layer#File%20Inclusion%20Configuration I guess this could be ported from the view config handler to the environment config handler. But we have to account for the possibility that someone might need to put a value like "-foo" in an array and not want it to cause some magic (Which is not much of an issue for HTML helpers, because they contain only parts of filenames, which usually don't start with "-" anyway) So some command with a "sf"-prefix might be better. standard_helpers: [">sf_remove:*", Partial] standard_helpers: [">sf_remove:Form"] Doesn't look too nice either... Any better ideas? :) Martin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
