Documented auto/forward/detach behaviour for chains in Intro

[catagits/Catalyst-Runtime.git] / lib / Catalyst / Manual / Intro.pod

diff --git a/lib/Catalyst/Manual/Intro.pod b/lib/Catalyst/Manual/Intro.pod
index 3eb9316..fe9ac8d 100644 (file)
--- a/lib/Catalyst/Manual/Intro.pod
+++ b/lib/Catalyst/Manual/Intro.pod
@@ -625,7 +625,7 @@ parts of the path (separated by C</>) this action wants to captures as
 it's arguments. If it doesn't expect any, just specify C<:Captures(0)>.
 The captures get passed to the action's C<@_> right after the context,
 but you can also find them as array reference in 
-C<$c-E<gt>request-E<gt>snippets-E<gt>[$level]>. The C<$level> is the
+C<$c-E<gt>request-E<gt>captures-E<gt>[$level]>. The C<$level> is the
 level of the action in the chain that captured the parts of the path.
 
 An action that is part of a chain (read: that has a C<:Chained> attribute)
@@ -651,6 +651,15 @@ C<$c-E<gt>request-E<gt>arguments>.
 
 =back
 
+Note that the list of C<auto> actions called depends on the private path
+of the endpoint of the chain, not on the chained actions way. The C<auto>
+actions will be run before the chain dispatching begins. In every other
+aspect, C<auto> actions behave as documented.
+
+The C<forward>ing to other actions does just what you would expect. But if
+you C<detach> out of a chain, the rest of the chain will not get called
+after the C<detach> returned.
+
 =item * B<Top-level> (B<Global>)
 
     package MyApp::Controller::Foo;