I think too that it is intuaive, and makes for easy to read code. Each page recieves the arguments, cleans the arguments, and processes the arguments. Calls to those processors are right there inside the method. Maybe a bit procedural, but simpler too.
matt
On 11/5/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Sean Cazzell wrote:
> Beside this, we still need to fix the turbogears.expose validators to
> work with positional arguments. One way is to require turbogears.expose
> to be the first decorator on your controller methods - this way it can
> use introspection to discover the names of your method's positional
> args. Does anyone have any objections to mandating that
> turbogears.expose be the first decorator?
>
> The other solution is to have another argument to turbogears.expose -
> something like positional_validators. But this is kind of ugly, IMHO.
>
IMO, the easiest and the cleanest way is not have turbogear handle the
validating. It is unnatural and I found it to be useless if I want to
do anything that is useful. Just receive the params as kwargs(which
cherrypy would support no matter what change will be there) then
validator it using schema or whatever within the handler.
