Prevent Browser Plugin to Navigate to Default Route in case of CANNOT_ACTIVATE Error

Hello, In my custom canActivate function I check if a user has the rights to access a specific route. If not then I manage to show a modal window to tell the user why he can’t do so.

The problem is that when manually changing the url in the browser then the browser plugin creates a different behaviour.

That is: on a CANNOT_ACTIVATE error my modal is correctly open but soon after this code will run and will redirect the user to the default page (home for example).

Is there a way to disable this behaviour? Whenever a user cannot activate a route (whether or not using the browser plugin) I want the user to remain where he was originally, my custom logic will take care of showing modal and/or redirect.

[troch]

@LeonardoGentile I’ll add an option to the browser plugin

[LeonardoGentile]

thank you @troch 👍

1. If we don’t specify defaultRoute then we will not get any redirection even for not found routes, right?

2. Instead of handling the multiple use cases (redirection on not found route, redirection on route that could not be activated, etcr) I guess that if you better document the errors listed here (ROUTE_NOT_FOUND, SAME_STATES, CANNOT_DEACTIVATE and so on) you could leave to the users (us) the logic for redirection

The second point is related to #176. It’s still not clear to me how to catch navigation error when manually changing the url when using the browser plugin. The browser plugin calls the router navigate method, but since we are not calling it manually we can’t pass error handlers to it.