Step 23.6: Use web version of Login component in routing

Urigo · Nov 27, 2016 · 6b0215e · 6b0215e
1 parent b4d8bf8
commit 6b0215e
Showing 1 changed file with 1 addition and 2 deletions.
diff --git a/client/imports/app/app.routes.ts b/client/imports/app/app.routes.ts
@@ -5,13 +5,12 @@ import { PartiesListComponent } from './parties/parties-list.component';
 import { PartyDetailsComponent } from './parties/party-details.component';
 import {SignupComponent} from "./auth/signup.component";
 import {RecoverComponent} from "./auth/recover.component";
-import {MobileLoginComponent} from "./auth/login.component.mobile";
 import {LoginComponent} from "./auth/login.component.web";
 
 export const routes: Route[] = [
   { path: '', component: PartiesListComponent },
   { path: 'party/:partyId', component: PartyDetailsComponent, canActivate: ['canActivateForLoggedIn'] },
-  { path: 'login', component: Meteor.isCordova ? MobileLoginComponent : LoginComponent },
+  { path: 'login', component: LoginComponent },
   { path: 'signup', component: SignupComponent },
   { path: 'recover', component: RecoverComponent }
 ];