move introspection closer to restrictive placeholders

mojolicious · Jan 26, 2016 · cee9134 · cee9134
1 parent 61612ae
commit cee9134
Showing 1 changed file with 12 additions and 12 deletions.
diff --git a/lib/Mojolicious/Guides/Routing.pod b/lib/Mojolicious/Guides/Routing.pod
@@ -527,6 +527,18 @@ non-capturing groups C<(?:...)> are fine though.
 This way you get easily readable routes and the raw power of regular
 expressions.
 
+=head2 Introspection
+
+The command L<Mojolicious::Command::routes> can be used from the command line
+to list all available routes together with names and underlying regular
+expressions.
+
+  $ ./myapp.pl routes -v
+  /foo/:name  ....  POST  fooname  ^/foo/([^/.]+)/?(?:\.([^/]+))?$
+  /bar        ..U.  *     bar      ^/bar
+    +/baz     ...W  GET   baz      ^/baz/?(?:\.([^/]+))?$
+  /yada       ....  *     yada     ^/yada/?(?:\.([^/]+))?$
+
 =head2 Under
 
 To share code with multiple nested routes you can use
@@ -789,18 +801,6 @@ You can even extend much of the core functionality.
 
 For a full list of available hooks see L<Mojolicious/"HOOKS">.
 
-=head2 Introspection
-
-The command L<Mojolicious::Command::routes> can be used from the command line
-to list all available routes together with names and underlying regular
-expressions.
-
-  $ ./myapp.pl routes -v
-  /foo/:name  ....  POST  fooname  ^/foo/([^/.]+)/?(?:\.([^/]+))?$
-  /bar        ..U.  *     bar      ^/bar
-    +/baz     ...W  GET   baz      ^/baz/?(?:\.([^/]+))?$
-  /yada       ....  *     yada     ^/yada/?(?:\.([^/]+))?$
-
 =head1 ADVANCED
 
 Less commonly used and more powerful features.