On Sun, Mar 23, 2008 at 4:57 PM, Wichert Akkerman <[EMAIL PROTECTED]> wrote:
> At the moment you get all four in one decorator. If you want a subset of > them you have to code the whole thing yourself. True, but it's not so bad. Look at the source. I stole elements of the @validate source to jack validation into my lib/base.py Controller superclass. Works fine, and allows me to redirect/dispatch as I want, conditionalize htmlfill, etc. I'm not sure what the > best way to make that more modular - we don't want to make the common > case more complex for developers. Making the last part optional feels > like a safe change to me: there are very good reasons to skip or do > custom output transformation, while there appear to be enough options > already to manage the first three. I agree. Validating the form against the schema seems like the "safe" best option. Inserting stuff into your html on-the-fly (especially if it can't handle one or more html types) doesn't seem "safe" at all... though it is pretty darn cool. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
