[EMAIL PROTECTED] said:
> Or maybe call it redirect_and_detach so other devs that may eventually
> need to read/debug the code can guess what it does without seeing what
> your definition of "stop" is =)
>
> always good to use known verbs =)
Sure. But I found some people stay away from "detach" be
>
> Wouldn't even need to. It's just an (untested)
>
> sub MyApp::redirect_and_stop {
> my $c = shift;
> $c->response->redirect(@_);
> $c->detach;
> }
>
> and a call via $c->redirect_and_stop( $c->uri_for('/foo', $foo) );
Or maybe call it redirect_and_detach so other dev
John Napiorkowski said:
> I didn't know you could detach without an arg. That
> sounds like want I want.
That's docced in Catalyst.pm, tho I think it was only added recently.
> I have to think I'm not the only one with this
> confusion. Maybe we could alias $c->end to $c->detach
> or something
--- Robert 'phaylon' Sedlacek <[EMAIL PROTECTED]>
wrote:
> John Napiorkowski said:
> > I have a controller with some chained actions.
> One of
> > the actions (not an endpoint) will redirect given
> a
> > certain value for the arguments. However I find
> that
> > this doesn't stop the chain fr
John Napiorkowski said:
> I have a controller with some chained actions. One of
> the actions (not an endpoint) will redirect given a
> certain value for the arguments. However I find that
> this doesn't stop the chain from completing. I still
> get a line about the redirect in the log, but the
John Napiorkowski wrote:
> Hi,
>
> I have a controller with some chained actions. One of
> the actions (not an endpoint) will redirect given a
> certain value for the arguments. However I find that
> this doesn't stop the chain from completing. I still
> get a line about the redirect in the log,
Hi,
I have a controller with some chained actions. One of
the actions (not an endpoint) will redirect given a
certain value for the arguments. However I find that
this doesn't stop the chain from completing. I still
get a line about the redirect in the log, but the
endpoint in that chain still