My question is straightforward and requires no elaborate explanation.
Can Durandal be configured to control the use of transitions when transitioning between viewmodels?
The motivation behind wanting to disable the animation is as follows:
I have a search form module quicksearch.js within my shell/masterpage that can be accessed from any page. It validates input and then redirects to the results page results.js, passing search parameters in the URL after the hash. The results.js handles querying the server.
When the quicksearch.js module is used on a page other than results.js, the animation is triggered, which is expected behavior. However, when on results.js and using quicksearch.js, only the parameter string in the URL changes (the module name after the hash remains the same). Despite this, the transition goes through the lifecycle of activating results.js again, resulting in an animation from results.js to itself, which looks unappealing.
Therefore, is there a way to conditionally prevent Durandal from animating content and instead just compose and bind the view?