Hi!
I finally got around to publishing a little plugin that we've had
running internally for some time now: Catalyst::Plugin::ExternalURI.
When you're working with CDNs or AWS S3 Buckets where you leave static
files like videos, css, js, etc (to have them served from S3) and you
have writt
This release of Catalyst tries to build more on our PSGI underpinnings. Here's
the changelog
- JSON Data handler looks for both JSON::MaybeXS and JSON, and uses
whichever is first (prefering to find JSON::MaybeXS). This should
improve compatibility as you likely already have one instal
My guess here is that path should be RO and that if you need to write code that
messed with the path, that should happen in plack middleware.
I'll ask around IRC to try and find out why this was allowed in the first
place. My guess it that we wanted to allow people to change the path for doing
You could also try to encapsulate the match logic in an action class or role.
--jnap
On Saturday, October 19, 2013 1:58 AM, Richard Thomas wrote:
> Any suggestions on how to do this? I'm toying with a large switch statement
> in the root controller and visiting the appropriate controller/ac
I'd probably myself want some plack middleware that would convert
/api/v1/account//widget/
to
/account//widget/ with accept type application/mycompany.v1+json
But you could probably support changing the URL path pretty easily with either
setting the controller namespace to have v1 in it,
>
> =head2 $req->path
>
Returns the path, i.e. the part of the URI after $req->base, for the
> current request.
Pasted below is Catalyst::Request's path method. Note from the final else
block that $req->path returns the request uri's path ($req->uri->path) with
the $req->base->path *removed*
