Assuming i’m currently in route ‘foo’, it sometimes make sense to requesting a model re-load for the same transition, but invoking TransitionToRoute(‘foo’) would not re-load the model due to:
Note that for routes with dynamic segments, this hook is only
executed when entered via the URL. If the route is entered through a transition (e.g. when using the `linkTo` Handlebars helper), then a model context is already provided and this hook is not called. Routes without dynamic segments will always execute the model hook.
But in situations such as performing some server invocation that changes too many properties in the model, I’d like to reload the model,
Currently I maintain dirty workarounds to achieve that but I’d like to have a better approach,
Does it make sense to extend the transition mechanism to allow model re-load even though the transition context already contains a model? or is there a better approach?