X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Runtime.git;a=blobdiff_plain;f=lib%2FCatalyst%2FDispatchType%2FChained.pm;h=dc9d1a37a88e148fc7735a18327497ee3dd356ef;hp=6705833e5737f78297da367ccaf10cef90b3e71c;hb=d9f0a350554cca79adefd4e97b4982d431f8c914;hpb=75ce30d0f208d49ead0134ab45fc2f45f72d6023 diff --git a/lib/Catalyst/DispatchType/Chained.pm b/lib/Catalyst/DispatchType/Chained.pm index 6705833..dc9d1a3 100644 --- a/lib/Catalyst/DispatchType/Chained.pm +++ b/lib/Catalyst/DispatchType/Chained.pm @@ -728,6 +728,10 @@ custom type constraints and import them into the controller namespace: sub int_priority_chain :Chained(chain_base) PathPart('') Args(Int) { } +If you use a reference type constraint in CaptureArgs, it must be a type +like Tuple in L that allows us to determine the number of +args to match. Otherwise this will raise an error during startup. + See L for more. =item Args @@ -748,6 +752,9 @@ Just as with C<:CaptureArgs>, the arguments get passed to the action in C<@_> after the context object. They can also be reached through C<$c-Erequest-Earguments>. +You should see 'Args' in L for more details on using +type constraints in your Args declarations. + =back =head2 Auto actions, dispatching and forwarding