Repository navigation
'needs' is too specific; we need a more flexible test #6
Description
What we have now is effectively "needs all". What about "needs only one" or "needs any"?
Possibly take a sub reference and let people use Syntax::Keyword::Junction:
use Syntax::Keyword::Junction qw/any one/;
my $spec = [
Param("foo")->needs( sub { $_ eq any(qw/bar baz/) } ),
Param("baz")->needs( sub { $_ eq one(qw/quux wibble/) } ),
];
Or, possibly we just make those individual methods (and use junctions internally):
my $spec = [
Param("foo")->needs_any(qw/bar baz/),
Param("baz")->needs_one(qw/quux wibble/),
];
Activity
bitbugprime commentedon Mar 27, 2013
How about adding "excludes" (or something similar) as well?
means that if foo is specified, bar may not also be specified.