Currently it is only reactive when used within the files app, because the files app
can access the vue router directly, problem is when other apps use it, then it is not reactive anymore
as they have a different Vue.
Also if you do not use Vue but vanilla JS or something else, the router params and query would not be reactive.
Problem that this is solving: React to route changes only, watching current view and query will trigger
on different time frames causing invalid states.
e.g. changing the view from A to B and the query from `/foo` to `/` will cause:
1. View change
2. query change
But after 1 the query is invalid and cause issues.
So this changes will allow listening the route change which is combined 1 & 2 -> valid state.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
dab678f7c5