implement a 404 page or disable temporarily the redirect mechanisms
With the current routing mechanism, it is quite easy to reroute the user to an existing route, as the route pattern is quite fixed (/:section/:subsection?/:accountId)
While trying to solve #863 (closed), the currentAccountId
will not be always defined. There will be intermediate states where guessing the currentAccountId
won't be that easy, and redirecting the user to the appropriate route will not be possible.
Which means at least for a temporary situation, we need to :
- either we create a 404 page and redirect the user to it when guessing the location is not possible
- either delete the current redirect mechanisms, when necessary, during the routing transition period, and implement it back when the migration is finished
@all what do you think ?
Edited by Antoine