there is such a background system, which is divided into many systems and modules, which involves a lot of operation permissions, and each lander is assigned different permissions, so the operable menus and visible pages are also different.
the previous scheme is to write the routing table of the full front-end page, and then filter Filter according to the routing table available to the lander returned by the background to get the actual displayable configuration, which is OK.
but on our platform, menus, permissions and modules can be configured, and the names and paths of these menus can be configured. As a result, once the business is modified, the error will be reported on the white screen if the front-end route is not correct, which is very fragile.
I have two questions:
1. If you first request to obtain the routing table = > mount route = > mount the vue instance, is this method of OK (failed attempt, always report error)?
2. In addition to server-side rendering, is there any other way to solve this kind of problem?