Jason Carreira wrote:
We'll have to agree to disagree :-) I think it's useful for some cases.
How about this one: You've got an action you want to alias multiple times with different defaults?
If that ever comes up, I'll answer it. So far I've never come across
such a situation, for me or anyone
> -Original Message-
> From: Rickard Öberg [mailto:[EMAIL PROTECTED]
>
> IIRC we argued about this before, and I think my position was
> that you'd
> typically want configuration to live elsewhere, but, as you said just
> don't use it (except that it becomes a built-in anti-pattern).
Jason Carreira wrote:
There are 2 types of parameterization, and you're free to use either
or both. The params in the configuration are static params which are
intended to parameterize a reusable Action for one or more aliases.
For instance, if you had an email action you might parameterize it
with
> -Original Message-
> From: Rickard Öberg [mailto:[EMAIL PROTECTED]
>
> Why are "params" declared explicitly? What's wrong with finding them
> implicitly, as is done in WebWork? Sounds like a refactoring disaster
> waiting to happen. Any configuration that is mostly just
> duplication
Jason Carreira wrote:
123
bar
456
foo
Why are "params" declared explicitly? What's wrong with finding
Carreira
Sent: February 27, 2003 2:51 AM
To: [EMAIL PROTECTED]
Subject: [OS-webwork] Commands implemented
I've just checked in the command code to xwork. It allows you to do
this:
123
bar
I've just checked in the command code to xwork. It allows you to do
this:
123
bar
456
foo
The comman
