use Moo ();
use Web::Dispatch::Wrapper ();
-our $VERSION = '0.019';
+our $VERSION = '0.020';
sub import {
my ($class, $app_package) = @_;
If you return a subroutine with a prototype, the prototype is treated
as a match specification - and if the test is passed, the body of the
-sub is called as a method any matched arguments (see below for more details).
+sub is called as a method and passed any matched arguments (see below for more details).
-You can also return a plain subroutine which will be called with just $env
-- remember that in this case if you need $self you -must- close over it.
+You can also return a plain subroutine which will be called with just C<$env>
+- remember that in this case if you need C<$self> you B<must> close over it.
If you return a normal object, L<Web::Simple> will simply return it upwards on
the assumption that a response_filter (or some arbitrary L<Plack::Middleware>)
the C<response_filter> we defined, after which the return is converted to a
true html response.
-However, two types of object are treated specially - a Plack::App object
-will have its C<->to_app> method called and be used as a dispatcher:
+However, two types of object are treated specially - a C<Plack::Component> object
+will have its C<to_app> method called and be used as a dispatcher:
sub dispatch_request {
my $self = shift;
...
}
-A Plack::Middleware object will be used as a filter for the rest of the
+A L<Plack::Middleware> object will be used as a filter for the rest of the
dispatch being returned into:
## responds to /admin/track_usage AND /admin/delete_accounts
},
}
-Note that this is for the dispatch being -returned- to, so if you want to
+Note that this is for the dispatch being B<returned> to, so if you want to
provide it inline you need to do:
## ALSO responds to /admin/track_usage AND /admin/delete_accounts
sub (/domain/*/user/*) {
my ($self, $domain, $user) = @_;
-and so on. To match an arbitrary number of parts, use -
+and so on. To match an arbitrary number of parts, use C<**>:
sub (/page/**) {
my ($self, $match) = @_;
to match an arbitrary number of parts up to but not including some final
part.
-Note: Since Web::Simple handles a concept of file extensions, * and **
+Note: Since Web::Simple handles a concept of file extensions, C<*> and C<**>
matchers will not by default match things after a final dot, and this
-can be modified by using *.* and **.* in the final position, i.e.:
+can be modified by using C<*.*> and C<**.*> in the final position, e.g.:
/one/* matches /one/two.three and captures "two"
/one/*.* matches /one/two.three and captures "two.three"
sub (/foo/...) {
-Will match C</foo/> on the beginning of the path -and- strip it. This is
+Will match C</foo/> on the beginning of the path B<and> strip it. This is
designed to be used to construct nested dispatch structures, but can also prove
useful for having e.g. an optional language specification at the start of a
path.
=head4 Naming your patch matches
-Any */**/*.*/**.* match can be followed with :name to make it into a named
+Any C<*>, C<**>, C<*.*>, or C<**.*> match can be followed with C<:name> to make it into a named
match, so:
sub (/*:one/*:two/*:three/*:four) {
sub (.html) {
will match .html from the path (assuming the subroutine itself returns
-something, of course). This is normally used for rendering - e.g.
+something, of course). This is normally used for rendering - e.g.:
sub (.html) {
response_filter { $self->render_html($_[1]) }
application/x-www-form-urlencoded or multipart/form-data - the latter
of which is required for uploads - see below.
-The param spec is elements of one of the following forms -
+The param spec is elements of one of the following forms:
param~ # optional parameter
param= # required parameter
* # include all other parameters in hashref
@* # include all other parameters as multiple in hashref
-separated by the & character. The arguments added to the request are
-one per non-:/* parameter (scalar for normal, arrayref for multiple),
-plus if any :/* specs exist a hashref containing those values.
+separated by the C<&> character. The arguments added to the request are
+one per non-C<:>/C<*> parameter (scalar for normal, arrayref for multiple),
+plus if any C<:>/C<*> specs exist a hashref containing those values.
Please note that if you specify a multiple type parameter match, you are
ensured of getting an arrayref for the value, EVEN if the current incoming
request has only one value. However if a parameter is specified as single
and multiple values are found, the last one will be used.
-For example to match a page parameter with an optional order_by parameter one
+For example to match a C<page> parameter with an optional C<order_by> parameter one
would write:
sub (?page=&order_by~) {
my ($self, $foo, $bar, $params);
where $bar is an arrayref (possibly an empty one), and $params contains
-arrayref values for all parameters -not- mentioned and a scalar value for
+arrayref values for all parameters B<not> mentioned and a scalar value for
the 'coffee' parameter.
Note, in the case where you combine arrayref, single parameter and named
=head3 Whitespace
-Note that for legibility you are permitted to use whitespace -
+Note that for legibility you are permitted to use whitespace:
sub (GET + /user/*) {
a hash reference as its first argument, the contained named parameters
will be accessible via C<%_>.
-This can be used to access your path matches, if they're named:
+This can be used to access your path matches, if they are named:
sub (GET + /foo/:path_part) {
[ 200,
],
}
-Note that only the first hash reference will be avaialble via C<%_>. If
+Note that only the first hash reference will be available via C<%_>. If
you receive additional hash references, you will need to access them as
usual.
=head3 Accessing the PSGI env hash
In some cases you may wish to get the raw PSGI env hash - to do this,
-you can either use a plain sub -
+you can either use a plain sub:
sub {
my ($env) = @_;
...
}
-or use the PSGI_ENV constant exported to retrieve it:
+or use the C<PSGI_ENV> constant exported to retrieve it from C<@_>:
sub (GET + /foo + ?some_param=) {
my $param = $_[1];
of continuing dispatch re-delegates it to the start of the dispatch process,
but with the path of the request altered to the supplied URL.
-Thus if you receive a POST to '/some/url' and return a redispatch to
-'/other/url', the dispatch behaviour will be exactly as if the same POST
-request had been made to '/other/url' instead.
+Thus if you receive a POST to C</some/url> and return a redispatch to
+C</other/url>, the dispatch behaviour will be exactly as if the same POST
+request had been made to C</other/url> instead.
Note, this is not the same as returning an HTTP 3xx redirect as a response;
rather it is a much more efficient internal process.
...
}
-Note that this method is still -returning- the dispatch code - just like
-dispatch did.
+Note that this method is still B<returning> the dispatch code - just like
+C<dispatch> did.
-Also note that you need the 'my $self = shift' since the magic $self
+Also note that you need the C<< my $self = shift >> since the magic $self
variable went away.
=item * the magic $self variable went away.
-Just add 'my $self = shift;' while writing your 'sub dispatch_request {'
+Just add C<< my $self = shift; >> while writing your C<< sub dispatch_request { >>
like a normal perl method.
=item * subdispatch deleted - all dispatchers can now subdispatch