Using computed navigationResolution

This change makes navigation for canceled navigation attempts, like CanDeactivate, navigate the opposite direction, instead of replacing the item in the history. Replacing the item in the history was corrupting the history when using location.back() and then canceling. I'm actually not sure why you would want to be messing with the history in the first place. 'computed' seems like the sensible option. If the user hits back, then cancels, the router cancels by going forward.

Author: josephmyers

src/SIL.XForge.Scripture/ClientApp/src/app/app-routing.module.ts

@@ -37,7 +37,11 @@ const routes: Routes = [
 ];
 
 @NgModule({
-  imports: [RouterModule.forRoot(routes)],
+  imports: [
+    RouterModule.forRoot(routes, {
+      canceledNavigationResolution: 'computed'
+    })
+  ],
   exports: [RouterModule]
 })
 export class AppRoutingModule {}