Alberto Valverde schrieb:
I think turbogears.util.to_kw and turbogears.util.from_kw would solve
the positional parameters issue. Something like this:
args, kw = to_kw(func, args, kw) # all params inside kw
kw = decode(kw)
kw = validate(kw)
args, kw = from_kw(func, args, kw) # positional params
Felix Schwarz wrote:
I spent some hours for this task and came to the conclusion, that we
can't implement this easily. The details are documented in the ticket
(together with a naive implementation):
http://trac.turbogears.org/ticket/1587#comment:2
If you have an idea, how to solve the
I spent some hours for this task and came to the conclusion, that we can't
implement this easily. The details are documented in the ticket (together with a
naive implementation):
http://trac.turbogears.org/ticket/1587#comment:2
If you have an idea, how to solve the problem for
Alberto Valverde wrote:
Felix Schwarz wrote:
Hi,
Alberto Valverde wrote:
IMO, this behavior belongs in the validate decorator, not in expose
which is already overcrowded.
Is expose really so big? Adding the filter would be a single line.
I'm referring more to the does way
Felix Schwarz wrote:
Hi,
Alberto Valverde wrote:
IMO, this behavior belongs in the validate decorator, not in expose
which is already overcrowded.
Is expose really so big? Adding the filter would be a single line.
I'm referring more to the does way too many things meaning of
Felix Schwarz wrote:
Hi,
Thomas Wittek filed ticket 1587 (http://trac.turbogears.org/ticket/1587).
IMHO, there should be a possibility to disable the variabledecode on a
by-function basis. Obviously, this is not possible with the current
implementation of NestedVariablesFilter as a
I think this makes good sense, and would be a good addition to TG 1.1.
Many of the decorators in TG2 just register data abut how the request
should be handled in the controller. But I think this belongs in
validate, and validate should be a real decorator, since it's
_supposed_to_ change the
