On 30.09.2010, at 11:09, Matt Robinson wrote: > Agreed, except that "safe" is misleading for another reason too - what could > possibly be safe about an unescaped string? :) "raw" would be much more > accurate. Copying the Filter extension and calling it "unsafe_raw" would be > even better. It's a necessary filter, but people ought to be discouraged from > using it unless they need to. Calling it "safe" makes it sound benign, rather > than potentially risky.
i like where you are going with this since its rarely used, imho it can be a fairly verbose, like "|noprotection" then again i think you currently have to use it where ever you output form widgets. regards, Lukas Kahwe Smith [email protected] -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com 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
