I have an Aurelia application where the user can select the company they're currently "working on". Every page in the app is dependent on the currently selected company, and the user can select a new company from a drop-down menu. The drop-down is a component sitting on the nav-bar.
What I'd like is to have that component reload the current page on the change.delegate
handler without restarting the app. So setting window.location.href
is out of the question.
Is there a way to force the aurelia Router
to reload the current route/page?
The alternative would be to use the EventAggregator
to signal a company change throughout the app, but that would require either subscribing to that event on every page or having every page inherit from a base class that subscribes to that event, but these are much more involved options.
This does not answer your exact question which is how to force a reload of the current view, but have you considered adding the current company identifier to your route(s)? This will solve your problem and make your routes bookmarkable: ie:
/#/company1/view1
and/#/company2/view1
. When you change the company in the drop-down you callrouter.navigate()
with the new route and the new view will be loaded/refreshed.To answer your exact question, I tested the
router.navigate
options:router.navigate('myroute', {replace:true, trigger:true})
and none of them force a reload of the view if the right view is already loaded. By appending?ramdomNumber
to your route name you can force a reactivation of the view.While not officially supported, there are a variety of
hackssuggestions in a relevant GitHub issue asking for this very functionality.The one I got to work that does not involve updating aurelia's source code nor adding superfluous data to the route is to set the
activationStrategy
on all of my routes to beinvokeLifecycle
instead of the default, like so:This makes it so the route's
activate()
method will run as you expect when the view model is reloaded. Then, in the code that initiates the reload, I do the following:Better answer:
The
navigateToRoute()
takes 3 parameters:trigger: true
option forces anactivationStrategy: invokeLifecycle
on this specific routing instruction without the need to set this option in the viewModel or routeConfig for normal routing.Here is a simple solution to refresh the page: in aurelia-history-browser.js, added a check in
updateHash()
and if the new _href is equal to the old then reload the page from the cache (not the server).Then, to refresh the page you just need to use the existing options:
The updated code is copied below: