can exit trigger prevent route change?

[jamgold]

I am trying to perform a check on route exit that should possible prevent the route to change (like form entries not saved). How can I abort the route change?

[arunoda]

Yes. It'll soon. We are working on that.

On Fri, Jun 19, 2015 at 1:13 AM Jan Hendrik Mangold <
notifications@github.com> wrote:

I am trying to perform a check on route exit that should possible prevent
the route to change (like form entries not saved). How can I abort the
route change?

—
Reply to this email directly or view it on GitHub
#170.

[arunoda]

I've just implemented it and waiting for others feedback. Could you have a look at this PR. There's a solution for you.

[jamgold]

I checked it with the PR but am not sure how it is supposed to work. Are you saying I should redirect(context.path) in the exit trigger to abort?

[arunoda]

Our redirect API need to have a URL everytime. So, you need to give it like above.

But, you are doing it in the exit handler, so still context.path is the current URL.
So, it tries to redirect to the same URL. Since we've idempotent URLs, route doesn't want.

may be you are looking for direct stop() API?

[jamgold]

may be you are looking for direct stop() API?

Yes, I think that would be clean(er).

[arunoda]

Got it.

[arunoda]

I think we will stick with the redirect API. You don't have a stop API.
If you need to do more validations, I prefer doing it before routing.

When user came to a exit trigger, stoping the route make no sense.
You need to at least change a query parameter to change it.

[jamgold]

OK, closing this issue then

[space-alien]

@jamgold my comments on #318 may be relevant.