Re: [Catalyst] Catalyst::Request path method as a setter

2013-10-22 Thread Bill Moseley
On Mon, Oct 21, 2013 at 9:13 AM, John Napiorkowski wrote: > 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. > Although I do want to let the app know what was removed from the path. Essentially, (for b

Re: [Catalyst] Catalyst::Request path method as a setter

2013-10-21 Thread John Napiorkowski
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

[Catalyst] Catalyst::Request path method as a setter

2013-10-21 Thread Bill Moseley
> > =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*