router: Incorrect routing when using navigationStrategy callback

Currently, I’m looking into dynamic routing in aurelia. To achieve this, I mapped all routes using a wildcard and I’m using the navigationStrategy property to determine the correct module id (as suggested in https://github.com/aurelia/router/issues/129).

configureRouter(config: RouterConfiguration, router: Router): void {
    config.map([
        { route: "**", nav: false, navigationStrategy: this.navigateToModule, settings: this }
    ]);

    router.handleUnknownRoutes(this.unknownRoutes);
}

private navigateToModule(instruction: NavigationInstruction): void {

// some logic to determine a moduleId
instruction.config.moduleId = moduleId; // A valid view-model
}

The first navigation is correct and loads the correct viewmodel, as expected. However, when I now navigate to another route in the same Router (with another moduleId), it always navigates to the current active viewmodel (instead of the new one). The navigationStrategy callback is called witch each navigation, as expected.

The activate() function of the current (incorrect) viewmodel is called, while the navigationInstruction.config.moduleId in the activate() function contains the new moduleId (as set in the navigateToModule function). When refreshing the site, the correct viewmodel is loaded.

The code is running on the current Aurelia release (beta.1.1.0), using Typescript. I’m encountering this in all browsers. Is this expected behavior?

I also tried to map the routes using the handleUnknownRoutes (as sugested in https://github.com/aurelia/router/issues/15). This is working as expected. However, I prefer to use the described way, since it is possible to use to settings property in the router better (there is no reference to the original class in the handleUnknownRoutes callback) and it is possible to use multiple wildcards and redirect them to other functions.