In this step we will authenticate and identify users in our app.
Before we go ahead and start extending our app, we will add a few packages which will make our lives a bit less complex when it comes to authentication and users management.
First we will update our Meteor server and add few Meteor packages called accounts-base and accounts-phone which will give us the ability to verify a user using an SMS code, so run the following inside api directory:
api$ meteor add accounts-base
api$ meteor add npm-bcrypt
api$ meteor add mys:accounts-phone
Be sure to keep your Meteor client script updated as well by running:
$ npm run meteor-client:bundle
For the sake of debugging we gonna write an authentication settings file (api/private/settings.json) which might make our life easier, but once you're in production mode you shouldn't use this configuration:
@@ -0,0 +1,8 @@
+┊ ┊1┊{
+┊ ┊2┊ "accounts-phone": {
+┊ ┊3┊ "verificationWaitTime": 0,
+┊ ┊4┊ "verificationRetriesWaitTime": 0,
+┊ ┊5┊ "adminPhoneNumbers": ["+9721234567", "+97212345678", "+97212345679"],
+┊ ┊6┊ "phoneVerificationMasterCode": "1234"
+┊ ┊7┊ }
+┊ ┊8┊}Now anytime we run our app we should provide it with a settings.json:
api$ meteor run --settings private/settings.json
To make it simpler we can add a script called api script to the package.json which will start the Meteor server:
@@ -9,6 +9,7 @@
┊ 9┊ 9┊ "url": "https://github.com/Urigo/Ionic2CLI-Meteor-WhatsApp.git"
┊10┊10┊ },
┊11┊11┊ "scripts": {
+┊ ┊12┊ "api": "cd api && meteor run --settings private/settings.json",
┊12┊13┊ "clean": "ionic-app-scripts clean",
┊13┊14┊ "build": "ionic-app-scripts build",
┊14┊15┊ "lint": "ionic-app-scripts lint",NOTE: If you would like to test the verification with a real phone number,
accounts-phoneprovides an easy access for twilio's API, for more information see accounts-phone's repo.
We will now apply the settings file we've just created so it can actually take effect:
@@ -3,8 +3,14 @@
┊ 3┊ 3┊import { Messages } from './collections/messages';
┊ 4┊ 4┊import * as moment from 'moment';
┊ 5┊ 5┊import { MessageType } from './models';
+┊ ┊ 6┊import { Accounts } from 'meteor/accounts-base';
┊ 6┊ 7┊
┊ 7┊ 8┊Meteor.startup(() => {
+┊ ┊ 9┊ if (Meteor.settings) {
+┊ ┊10┊ Object.assign(Accounts._options, Meteor.settings['accounts-phone']);
+┊ ┊11┊ SMS.twilio = Meteor.settings['twilio'];
+┊ ┊12┊ }
+┊ ┊13┊
┊ 8┊14┊ if (Chats.find({}).cursor.count() === 0) {
┊ 9┊15┊ let chatId;We also need to make sure we have the necessary declaration files for the package we've just added, so the compiler can recognize the new API:
$ npm install --save-dev @types/meteor-accounts-phone
And we will reference from the tsconfig like so:
@@ -16,7 +16,8 @@
┊16┊16┊ "stripInternal": true,
┊17┊17┊ "noImplicitAny": false,
┊18┊18┊ "types": [
-┊19┊ ┊ "@types/meteor"
+┊ ┊19┊ "@types/meteor",
+┊ ┊20┊ "@types/meteor-accounts-phone"
┊20┊21┊ ]
┊21┊22┊ },
┊22┊23┊ "exclude": [Now, we will use the Meteor's accounts system in the client. Our first use case would be delaying our app's bootstrap phase, until Meteor's accounts system has done it's initialization.
Meteor's accounts API exposes a method called loggingIn which indicates if the authentication flow is done, which we gonna use before bootstraping our application, to make sure we provide the client with the necessary views which are right to his current state:
@@ -1,7 +1,18 @@
┊ 1┊ 1┊import 'meteor-client';
┊ 2┊ 2┊
┊ 3┊ 3┊import { platformBrowserDynamic } from '@angular/platform-browser-dynamic';
-┊ 4┊ ┊
+┊ ┊ 4┊import { MeteorObservable } from 'meteor-rxjs';
+┊ ┊ 5┊import { Meteor } from 'meteor/meteor';
┊ 5┊ 6┊import { AppModule } from './app.module';
┊ 6┊ 7┊
-┊ 7┊ ┊platformBrowserDynamic().bootstrapModule(AppModule);
+┊ ┊ 8┊Meteor.startup(() => {
+┊ ┊ 9┊ const subscription = MeteorObservable.autorun().subscribe(() => {
+┊ ┊10┊
+┊ ┊11┊ if (Meteor.loggingIn()) {
+┊ ┊12┊ return;
+┊ ┊13┊ }
+┊ ┊14┊
+┊ ┊15┊ setTimeout(() => subscription.unsubscribe());
+┊ ┊16┊ platformBrowserDynamic().bootstrapModule(AppModule);
+┊ ┊17┊ });
+┊ ┊18┊});To make things easier, we're going to organize all authentication related functions into a single service which we're gonna call PhoneService:
@@ -0,0 +1,42 @@
+┊ ┊ 1┊import { Injectable } from '@angular/core';
+┊ ┊ 2┊import { Accounts } from 'meteor/accounts-base';
+┊ ┊ 3┊import { Meteor } from 'meteor/meteor';
+┊ ┊ 4┊
+┊ ┊ 5┊@Injectable()
+┊ ┊ 6┊export class PhoneService {
+┊ ┊ 7┊ verify(phoneNumber: string): Promise<void> {
+┊ ┊ 8┊ return new Promise<void>((resolve, reject) => {
+┊ ┊ 9┊ Accounts.requestPhoneVerification(phoneNumber, (e: Error) => {
+┊ ┊10┊ if (e) {
+┊ ┊11┊ return reject(e);
+┊ ┊12┊ }
+┊ ┊13┊
+┊ ┊14┊ resolve();
+┊ ┊15┊ });
+┊ ┊16┊ });
+┊ ┊17┊ }
+┊ ┊18┊
+┊ ┊19┊ login(phoneNumber: string, code: string): Promise<void> {
+┊ ┊20┊ return new Promise<void>((resolve, reject) => {
+┊ ┊21┊ Accounts.verifyPhone(phoneNumber, code, (e: Error) => {
+┊ ┊22┊ if (e) {
+┊ ┊23┊ return reject(e);
+┊ ┊24┊ }
+┊ ┊25┊
+┊ ┊26┊ resolve();
+┊ ┊27┊ });
+┊ ┊28┊ });
+┊ ┊29┊ }
+┊ ┊30┊
+┊ ┊31┊ logout(): Promise<void> {
+┊ ┊32┊ return new Promise<void>((resolve, reject) => {
+┊ ┊33┊ Meteor.logout((e: Error) => {
+┊ ┊34┊ if (e) {
+┊ ┊35┊ return reject(e);
+┊ ┊36┊ }
+┊ ┊37┊
+┊ ┊38┊ resolve();
+┊ ┊39┊ });
+┊ ┊40┊ });
+┊ ┊41┊ }
+┊ ┊42┊}And we gonna require it in the app's NgModule so it can be recognized:
@@ -6,6 +6,7 @@
┊ 6┊ 6┊import { MomentModule } from 'angular2-moment';
┊ 7┊ 7┊import { ChatsPage } from '../pages/chats/chats';
┊ 8┊ 8┊import { MessagesPage } from '../pages/messages/messages';
+┊ ┊ 9┊import { PhoneService } from '../services/phone';
┊ 9┊10┊import { MyApp } from './app.component';
┊10┊11┊
┊11┊12┊@NgModule({@@ -28,7 +29,8 @@
┊28┊29┊ providers: [
┊29┊30┊ StatusBar,
┊30┊31┊ SplashScreen,
-┊31┊ ┊ {provide: ErrorHandler, useClass: IonicErrorHandler}
+┊ ┊32┊ {provide: ErrorHandler, useClass: IonicErrorHandler},
+┊ ┊33┊ PhoneService
┊32┊34┊ ]
┊33┊35┊})
┊34┊36┊export class AppModule {}The PhoneService is not only packed with whatever functionality we need, but it also wraps async callbacks with promises, which has several advantages:
- A promise is chainable, and provides an easy way to manage an async flow.
- A promise is wrapped with
zone, which means the view will be updated automatically once the callback has been invoked. - A promise can interface with an
Observable.
Just so the TypeScript compiler will know how to digest it, we shall also specify the accounts-phone types in the client tsconfig.json as well:
@@ -20,7 +20,8 @@
┊20┊20┊ "stripInternal": true,
┊21┊21┊ "noImplicitAny": false,
┊22┊22┊ "types": [
-┊23┊ ┊ "@types/meteor"
+┊ ┊23┊ "@types/meteor",
+┊ ┊24┊ "@types/meteor-accounts-phone"
┊24┊25┊ ]
┊25┊26┊ },
┊26┊27┊ "include": [For authentication purposes, we gonna create the following flow in our app:
- login - The initial page in the authentication flow where the user fills up his phone number.
- verification - Verify a user's phone number by an SMS authentication.
- profile - Ask a user to pickup its name. Afterwards he will be promoted to the tabs page.
Let's start by creating the LoginComponent. In this component we will request an SMS verification right after a phone number has been entered:
@@ -0,0 +1,66 @@
+┊ ┊ 1┊import { Component } from '@angular/core';
+┊ ┊ 2┊import { Alert, AlertController, NavController } from 'ionic-angular';
+┊ ┊ 3┊import { PhoneService } from '../../services/phone';
+┊ ┊ 4┊
+┊ ┊ 5┊@Component({
+┊ ┊ 6┊ selector: 'login',
+┊ ┊ 7┊ templateUrl: 'login.html'
+┊ ┊ 8┊})
+┊ ┊ 9┊export class LoginPage {
+┊ ┊10┊ private phone = '';
+┊ ┊11┊
+┊ ┊12┊ constructor(
+┊ ┊13┊ private alertCtrl: AlertController,
+┊ ┊14┊ private phoneService: PhoneService,
+┊ ┊15┊ private navCtrl: NavController
+┊ ┊16┊ ) {}
+┊ ┊17┊
+┊ ┊18┊ onInputKeypress({keyCode}: KeyboardEvent): void {
+┊ ┊19┊ if (keyCode === 13) {
+┊ ┊20┊ this.login();
+┊ ┊21┊ }
+┊ ┊22┊ }
+┊ ┊23┊
+┊ ┊24┊ login(phone: string = this.phone): void {
+┊ ┊25┊ const alert = this.alertCtrl.create({
+┊ ┊26┊ title: 'Confirm',
+┊ ┊27┊ message: `Would you like to proceed with the phone number ${phone}?`,
+┊ ┊28┊ buttons: [
+┊ ┊29┊ {
+┊ ┊30┊ text: 'Cancel',
+┊ ┊31┊ role: 'cancel'
+┊ ┊32┊ },
+┊ ┊33┊ {
+┊ ┊34┊ text: 'Yes',
+┊ ┊35┊ handler: () => {
+┊ ┊36┊ this.handleLogin(alert);
+┊ ┊37┊ return false;
+┊ ┊38┊ }
+┊ ┊39┊ }
+┊ ┊40┊ ]
+┊ ┊41┊ });
+┊ ┊42┊
+┊ ┊43┊ alert.present();
+┊ ┊44┊ }
+┊ ┊45┊
+┊ ┊46┊ handleLogin(alert: Alert): void {
+┊ ┊47┊ alert.dismiss().then(() => {
+┊ ┊48┊ return this.phoneService.verify(this.phone);
+┊ ┊49┊ })
+┊ ┊50┊ .catch((e) => {
+┊ ┊51┊ this.handleError(e);
+┊ ┊52┊ });
+┊ ┊53┊ }
+┊ ┊54┊
+┊ ┊55┊ handleError(e: Error): void {
+┊ ┊56┊ console.error(e);
+┊ ┊57┊
+┊ ┊58┊ const alert = this.alertCtrl.create({
+┊ ┊59┊ title: 'Oops!',
+┊ ┊60┊ message: e.message,
+┊ ┊61┊ buttons: ['OK']
+┊ ┊62┊ });
+┊ ┊63┊
+┊ ┊64┊ alert.present();
+┊ ┊65┊ }
+┊ ┊66┊}In short, once we press the login button, the login method is called and shows an alert dialog to confirm the action (See reference). If an error has occurred, the handlerError method is called and shows an alert dialog with the received error. If everything went as expected the handleLogin method is invoked, which will call the login method in the PhoneService.
Hopefully that the component's logic is clear now, let's move to the template:
@@ -0,0 +1,25 @@
+┊ ┊ 1┊<ion-header>
+┊ ┊ 2┊ <ion-navbar color="whatsapp">
+┊ ┊ 3┊ <ion-title>Login</ion-title>
+┊ ┊ 4┊
+┊ ┊ 5┊ <ion-buttons end>
+┊ ┊ 6┊ <button ion-button class="done-button" (click)="login()">Done</button>
+┊ ┊ 7┊ </ion-buttons>
+┊ ┊ 8┊ </ion-navbar>
+┊ ┊ 9┊</ion-header>
+┊ ┊10┊
+┊ ┊11┊<ion-content padding class="login-page-content">
+┊ ┊12┊ <div class="instructions">
+┊ ┊13┊ <div>
+┊ ┊14┊ Please enter your phone number including its country code.
+┊ ┊15┊ </div>
+┊ ┊16┊ <br>
+┊ ┊17┊ <div>
+┊ ┊18┊ The messenger will send a one time SMS message to verify your phone number. Carrier SMS charges may apply.
+┊ ┊19┊ </div>
+┊ ┊20┊ </div>
+┊ ┊21┊
+┊ ┊22┊ <ion-item>
+┊ ┊23┊ <ion-input [(ngModel)]="phone" (keypress)="onInputKeypress($event)" type="tel" placeholder="Your phone number"></ion-input>
+┊ ┊24┊ </ion-item>
+┊ ┊25┊</ion-content>And add some style into it:
@@ -0,0 +1,11 @@
+┊ ┊ 1┊.login-page-content {
+┊ ┊ 2┊ .instructions {
+┊ ┊ 3┊ text-align: center;
+┊ ┊ 4┊ font-size: medium;
+┊ ┊ 5┊ margin: 50px;
+┊ ┊ 6┊ }
+┊ ┊ 7┊
+┊ ┊ 8┊ .text-input {
+┊ ┊ 9┊ text-align: center;
+┊ ┊10┊ }
+┊ ┊11┊}And as usual, newly created components should be imported in the app's module:
@@ -5,6 +5,7 @@
┊ 5┊ 5┊import { StatusBar } from '@ionic-native/status-bar';
┊ 6┊ 6┊import { MomentModule } from 'angular2-moment';
┊ 7┊ 7┊import { ChatsPage } from '../pages/chats/chats';
+┊ ┊ 8┊import { LoginPage } from '../pages/login/login';
┊ 8┊ 9┊import { MessagesPage } from '../pages/messages/messages';
┊ 9┊10┊import { PhoneService } from '../services/phone';
┊10┊11┊import { MyApp } from './app.component';@@ -13,7 +14,8 @@
┊13┊14┊ declarations: [
┊14┊15┊ MyApp,
┊15┊16┊ ChatsPage,
-┊16┊ ┊ MessagesPage
+┊ ┊17┊ MessagesPage,
+┊ ┊18┊ LoginPage
┊17┊19┊ ],
┊18┊20┊ imports: [
┊19┊21┊ BrowserModule,@@ -24,7 +26,8 @@
┊24┊26┊ entryComponents: [
┊25┊27┊ MyApp,
┊26┊28┊ ChatsPage,
-┊27┊ ┊ MessagesPage
+┊ ┊29┊ MessagesPage,
+┊ ┊30┊ LoginPage
┊28┊31┊ ],
┊29┊32┊ providers: [
┊30┊33┊ StatusBar,We will also need to identify if the user is logged in or not once the app is launched; If so - the user will be promoted directly to the ChatsPage, and if not, he will have to go through the LoginPage first:
@@ -3,14 +3,18 @@
┊ 3┊ 3┊import { StatusBar } from '@ionic-native/status-bar';
┊ 4┊ 4┊import { SplashScreen } from '@ionic-native/splash-screen';
┊ 5┊ 5┊import { ChatsPage } from '../pages/chats/chats';
+┊ ┊ 6┊import { Meteor } from 'meteor/meteor';
+┊ ┊ 7┊import { LoginPage } from '../pages/login/login';
┊ 6┊ 8┊
┊ 7┊ 9┊@Component({
┊ 8┊10┊ templateUrl: 'app.html'
┊ 9┊11┊})
┊10┊12┊export class MyApp {
-┊11┊ ┊ rootPage:any = ChatsPage;
+┊ ┊13┊ rootPage: any;
┊12┊14┊
┊13┊15┊ constructor(platform: Platform, statusBar: StatusBar, splashScreen: SplashScreen) {
+┊ ┊16┊ this.rootPage = Meteor.user() ? ChatsPage : LoginPage;
+┊ ┊17┊
┊14┊18┊ platform.ready().then(() => {
┊15┊19┊ // Okay, so the platform is ready and our plugins are available.
┊16┊20┊ // Here you can do any higher level native things you might need.Let's proceed and implement the verification page. We will start by creating its component, called VerificationPage. Logic is pretty much the same as in the LoginComponent:
@@ -0,0 +1,48 @@
+┊ ┊ 1┊import { Component, OnInit } from '@angular/core';
+┊ ┊ 2┊import { AlertController, NavController, NavParams } from 'ionic-angular';
+┊ ┊ 3┊import { PhoneService } from '../../services/phone';
+┊ ┊ 4┊
+┊ ┊ 5┊@Component({
+┊ ┊ 6┊ selector: 'verification',
+┊ ┊ 7┊ templateUrl: 'verification.html'
+┊ ┊ 8┊})
+┊ ┊ 9┊export class VerificationPage implements OnInit {
+┊ ┊10┊ private code: string = '';
+┊ ┊11┊ private phone: string;
+┊ ┊12┊
+┊ ┊13┊ constructor(
+┊ ┊14┊ private alertCtrl: AlertController,
+┊ ┊15┊ private navCtrl: NavController,
+┊ ┊16┊ private navParams: NavParams,
+┊ ┊17┊ private phoneService: PhoneService
+┊ ┊18┊ ) {}
+┊ ┊19┊
+┊ ┊20┊ ngOnInit() {
+┊ ┊21┊ this.phone = this.navParams.get('phone');
+┊ ┊22┊ }
+┊ ┊23┊
+┊ ┊24┊ onInputKeypress({keyCode}: KeyboardEvent): void {
+┊ ┊25┊ if (keyCode === 13) {
+┊ ┊26┊ this.verify();
+┊ ┊27┊ }
+┊ ┊28┊ }
+┊ ┊29┊
+┊ ┊30┊ verify(): void {
+┊ ┊31┊ this.phoneService.login(this.phone, this.code)
+┊ ┊32┊ .catch((e) => {
+┊ ┊33┊ this.handleError(e);
+┊ ┊34┊ });
+┊ ┊35┊ }
+┊ ┊36┊
+┊ ┊37┊ handleError(e: Error): void {
+┊ ┊38┊ console.error(e);
+┊ ┊39┊
+┊ ┊40┊ const alert = this.alertCtrl.create({
+┊ ┊41┊ title: 'Oops!',
+┊ ┊42┊ message: e.message,
+┊ ┊43┊ buttons: ['OK']
+┊ ┊44┊ });
+┊ ┊45┊
+┊ ┊46┊ alert.present();
+┊ ┊47┊ }
+┊ ┊48┊}@@ -0,0 +1,25 @@
+┊ ┊ 1┊<ion-header>
+┊ ┊ 2┊ <ion-navbar color="whatsapp">
+┊ ┊ 3┊ <ion-title>Verification</ion-title>
+┊ ┊ 4┊
+┊ ┊ 5┊ <ion-buttons end>
+┊ ┊ 6┊ <button ion-button class="verify-button" (click)="verify()">Verify</button>
+┊ ┊ 7┊ </ion-buttons>
+┊ ┊ 8┊ </ion-navbar>
+┊ ┊ 9┊</ion-header>
+┊ ┊10┊
+┊ ┊11┊<ion-content padding class="verification-page-content">
+┊ ┊12┊ <div class="instructions">
+┊ ┊13┊ <div>
+┊ ┊14┊ An SMS message with the verification code has been sent to {{phone}}.
+┊ ┊15┊ </div>
+┊ ┊16┊ <br>
+┊ ┊17┊ <div>
+┊ ┊18┊ To proceed, please enter the 4-digit verification code below.
+┊ ┊19┊ </div>
+┊ ┊20┊ </div>
+┊ ┊21┊
+┊ ┊22┊ <ion-item>
+┊ ┊23┊ <ion-input [(ngModel)]="code" (keypress)="onInputKeypress($event)" type="tel" placeholder="Your verification code"></ion-input>
+┊ ┊24┊ </ion-item>
+┊ ┊25┊</ion-content>@@ -0,0 +1,11 @@
+┊ ┊ 1┊.verification-page-content {
+┊ ┊ 2┊ .instructions {
+┊ ┊ 3┊ text-align: center;
+┊ ┊ 4┊ font-size: medium;
+┊ ┊ 5┊ margin: 50px;
+┊ ┊ 6┊ }
+┊ ┊ 7┊
+┊ ┊ 8┊ .text-input {
+┊ ┊ 9┊ text-align: center;
+┊ ┊10┊ }
+┊ ┊11┊}And add it to the NgModule:
@@ -7,6 +7,7 @@
┊ 7┊ 7┊import { ChatsPage } from '../pages/chats/chats';
┊ 8┊ 8┊import { LoginPage } from '../pages/login/login';
┊ 9┊ 9┊import { MessagesPage } from '../pages/messages/messages';
+┊ ┊10┊import { VerificationPage } from '../pages/verification/verification';
┊10┊11┊import { PhoneService } from '../services/phone';
┊11┊12┊import { MyApp } from './app.component';
┊12┊13┊@@ -15,7 +16,8 @@
┊15┊16┊ MyApp,
┊16┊17┊ ChatsPage,
┊17┊18┊ MessagesPage,
-┊18┊ ┊ LoginPage
+┊ ┊19┊ LoginPage,
+┊ ┊20┊ VerificationPage
┊19┊21┊ ],
┊20┊22┊ imports: [
┊21┊23┊ BrowserModule,@@ -27,7 +29,8 @@
┊27┊29┊ MyApp,
┊28┊30┊ ChatsPage,
┊29┊31┊ MessagesPage,
-┊30┊ ┊ LoginPage
+┊ ┊32┊ LoginPage,
+┊ ┊33┊ VerificationPage
┊31┊34┊ ],
┊32┊35┊ providers: [
┊33┊36┊ StatusBar,Now we can make sure that anytime we login, we will be promoted to the VerificationPage right after:
@@ -1,6 +1,7 @@
┊1┊1┊import { Component } from '@angular/core';
┊2┊2┊import { Alert, AlertController, NavController } from 'ionic-angular';
┊3┊3┊import { PhoneService } from '../../services/phone';
+┊ ┊4┊import { VerificationPage } from '../verification/verification';
┊4┊5┊
┊5┊6┊@Component({
┊6┊7┊ selector: 'login',@@ -47,6 +48,11 @@
┊47┊48┊ alert.dismiss().then(() => {
┊48┊49┊ return this.phoneService.verify(this.phone);
┊49┊50┊ })
+┊ ┊51┊ .then(() => {
+┊ ┊52┊ this.navCtrl.push(VerificationPage, {
+┊ ┊53┊ phone: this.phone
+┊ ┊54┊ });
+┊ ┊55┊ })
┊50┊56┊ .catch((e) => {
┊51┊57┊ this.handleError(e);
┊52┊58┊ });The last step in our authentication pattern is setting our profile. We will create a Profile interface so the compiler can recognize profile-data structures:
@@ -1,3 +1,10 @@
+┊ ┊ 1┊export const DEFAULT_PICTURE_URL = '/assets/default-profile-pic.svg';
+┊ ┊ 2┊
+┊ ┊ 3┊export interface Profile {
+┊ ┊ 4┊ name?: string;
+┊ ┊ 5┊ picture?: string;
+┊ ┊ 6┊}
+┊ ┊ 7┊
┊ 1┊ 8┊export enum MessageType {
┊ 2┊ 9┊ TEXT = <any>'text'
┊ 3┊10┊}As you can probably notice we also defined a constant for the default profile picture. We will need to make this resource available for use before proceeding. The referenced svg file can be copied directly from the ionicons NodeJS module using the following command:
src/assets$ cp ../../node_modules/ionicons/dist/svg/ios-contact.svg default-profile-pic.svg
Now we can safely proceed to implementing the ProfileComponent:
@@ -0,0 +1,48 @@
+┊ ┊ 1┊import { Component, OnInit } from '@angular/core';
+┊ ┊ 2┊import { Profile } from 'api/models';
+┊ ┊ 3┊import { AlertController, NavController } from 'ionic-angular';
+┊ ┊ 4┊import { MeteorObservable } from 'meteor-rxjs';
+┊ ┊ 5┊import { ChatsPage } from '../chats/chats';
+┊ ┊ 6┊
+┊ ┊ 7┊@Component({
+┊ ┊ 8┊ selector: 'profile',
+┊ ┊ 9┊ templateUrl: 'profile.html'
+┊ ┊10┊})
+┊ ┊11┊export class ProfilePage implements OnInit {
+┊ ┊12┊ picture: string;
+┊ ┊13┊ profile: Profile;
+┊ ┊14┊
+┊ ┊15┊ constructor(
+┊ ┊16┊ private alertCtrl: AlertController,
+┊ ┊17┊ private navCtrl: NavController
+┊ ┊18┊ ) {}
+┊ ┊19┊
+┊ ┊20┊ ngOnInit(): void {
+┊ ┊21┊ this.profile = Meteor.user().profile || {
+┊ ┊22┊ name: ''
+┊ ┊23┊ };
+┊ ┊24┊ }
+┊ ┊25┊
+┊ ┊26┊ updateProfile(): void {
+┊ ┊27┊ MeteorObservable.call('updateProfile', this.profile).subscribe({
+┊ ┊28┊ next: () => {
+┊ ┊29┊ this.navCtrl.push(ChatsPage);
+┊ ┊30┊ },
+┊ ┊31┊ error: (e: Error) => {
+┊ ┊32┊ this.handleError(e);
+┊ ┊33┊ }
+┊ ┊34┊ });
+┊ ┊35┊ }
+┊ ┊36┊
+┊ ┊37┊ handleError(e: Error): void {
+┊ ┊38┊ console.error(e);
+┊ ┊39┊
+┊ ┊40┊ const alert = this.alertCtrl.create({
+┊ ┊41┊ title: 'Oops!',
+┊ ┊42┊ message: e.message,
+┊ ┊43┊ buttons: ['OK']
+┊ ┊44┊ });
+┊ ┊45┊
+┊ ┊46┊ alert.present();
+┊ ┊47┊ }
+┊ ┊48┊}@@ -0,0 +1,20 @@
+┊ ┊ 1┊<ion-header>
+┊ ┊ 2┊ <ion-navbar color="whatsapp">
+┊ ┊ 3┊ <ion-title>Profile</ion-title>
+┊ ┊ 4┊
+┊ ┊ 5┊ <ion-buttons end>
+┊ ┊ 6┊ <button ion-button class="done-button" (click)="updateProfile()">Done</button>
+┊ ┊ 7┊ </ion-buttons>
+┊ ┊ 8┊ </ion-navbar>
+┊ ┊ 9┊</ion-header>
+┊ ┊10┊
+┊ ┊11┊<ion-content class="profile-page-content">
+┊ ┊12┊ <div class="profile-picture">
+┊ ┊13┊ <img *ngIf="picture" [src]="picture">
+┊ ┊14┊ </div>
+┊ ┊15┊
+┊ ┊16┊ <ion-item class="profile-name">
+┊ ┊17┊ <ion-label stacked>Name</ion-label>
+┊ ┊18┊ <ion-input [(ngModel)]="profile.name" placeholder="Your name"></ion-input>
+┊ ┊19┊ </ion-item>
+┊ ┊20┊</ion-content>@@ -0,0 +1,20 @@
+┊ ┊ 1┊.profile-page-content {
+┊ ┊ 2┊ .profile-picture {
+┊ ┊ 3┊ max-width: 300px;
+┊ ┊ 4┊ display: block;
+┊ ┊ 5┊ margin: auto;
+┊ ┊ 6┊
+┊ ┊ 7┊ img {
+┊ ┊ 8┊ margin-bottom: -33px;
+┊ ┊ 9┊ width: 100%;
+┊ ┊10┊ }
+┊ ┊11┊
+┊ ┊12┊ ion-icon {
+┊ ┊13┊ float: right;
+┊ ┊14┊ font-size: 30px;
+┊ ┊15┊ opacity: 0.5;
+┊ ┊16┊ border-left: black solid 1px;
+┊ ┊17┊ padding-left: 5px;
+┊ ┊18┊ }
+┊ ┊19┊ }
+┊ ┊20┊}Let's redirect users who passed the verification stage to the newly created ProfileComponent like so:
@@ -1,6 +1,7 @@
┊1┊1┊import { Component, OnInit } from '@angular/core';
┊2┊2┊import { AlertController, NavController, NavParams } from 'ionic-angular';
┊3┊3┊import { PhoneService } from '../../services/phone';
+┊ ┊4┊import { ProfilePage } from '../profile/profile';
┊4┊5┊
┊5┊6┊@Component({
┊6┊7┊ selector: 'verification',@@ -28,7 +29,11 @@
┊28┊29┊ }
┊29┊30┊
┊30┊31┊ verify(): void {
-┊31┊ ┊ this.phoneService.login(this.phone, this.code)
+┊ ┊32┊ this.phoneService.login(this.phone, this.code).then(() => {
+┊ ┊33┊ this.navCtrl.setRoot(ProfilePage, {}, {
+┊ ┊34┊ animate: true
+┊ ┊35┊ });
+┊ ┊36┊ })
┊32┊37┊ .catch((e) => {
┊33┊38┊ this.handleError(e);
┊34┊39┊ });We will also need to import the ProfileComponent in the app's NgModule so it can be recognized:
@@ -7,6 +7,7 @@
┊ 7┊ 7┊import { ChatsPage } from '../pages/chats/chats';
┊ 8┊ 8┊import { LoginPage } from '../pages/login/login';
┊ 9┊ 9┊import { MessagesPage } from '../pages/messages/messages';
+┊ ┊10┊import { ProfilePage } from '../pages/profile/profile';
┊10┊11┊import { VerificationPage } from '../pages/verification/verification';
┊11┊12┊import { PhoneService } from '../services/phone';
┊12┊13┊import { MyApp } from './app.component';@@ -17,7 +18,8 @@
┊17┊18┊ ChatsPage,
┊18┊19┊ MessagesPage,
┊19┊20┊ LoginPage,
-┊20┊ ┊ VerificationPage
+┊ ┊21┊ VerificationPage,
+┊ ┊22┊ ProfilePage
┊21┊23┊ ],
┊22┊24┊ imports: [
┊23┊25┊ BrowserModule,@@ -30,7 +32,8 @@
┊30┊32┊ ChatsPage,
┊31┊33┊ MessagesPage,
┊32┊34┊ LoginPage,
-┊33┊ ┊ VerificationPage
+┊ ┊35┊ VerificationPage,
+┊ ┊36┊ ProfilePage
┊34┊37┊ ],
┊35┊38┊ providers: [
┊36┊39┊ StatusBar,The core logic behind this component actually lies within the invocation of the updateProfile, a Meteor method implemented in our API which looks like so:
@@ -1,6 +1,6 @@
┊1┊1┊import { Chats } from './collections/chats';
┊2┊2┊import { Messages } from './collections/messages';
-┊3┊ ┊import { MessageType } from './models';
+┊ ┊3┊import { MessageType, Profile } from './models';
┊4┊4┊import { check, Match } from 'meteor/check';
┊5┊5┊
┊6┊6┊const nonEmptyString = Match.Where((str) => {@@ -9,6 +9,18 @@
┊ 9┊ 9┊});
┊10┊10┊
┊11┊11┊Meteor.methods({
+┊ ┊12┊ updateProfile(profile: Profile): void {
+┊ ┊13┊ if (!this.userId) throw new Meteor.Error('unauthorized',
+┊ ┊14┊ 'User must be logged-in to create a new chat');
+┊ ┊15┊
+┊ ┊16┊ check(profile, {
+┊ ┊17┊ name: nonEmptyString
+┊ ┊18┊ });
+┊ ┊19┊
+┊ ┊20┊ Meteor.users.update(this.userId, {
+┊ ┊21┊ $set: {profile}
+┊ ┊22┊ });
+┊ ┊23┊ },
┊12┊24┊ addMessage(type: MessageType, chatId: string, content: string) {
┊13┊25┊ check(type, Match.OneOf(String, [ MessageType.TEXT ]));
┊14┊26┊ check(chatId, nonEmptyString);Now that our authentication flow is complete, we will need to edit the messages, so each user can be identified by each message sent. We will add a restriction in the addMessage method to see if a user is logged in, and we will bind its ID to the created message:
@@ -22,6 +22,9 @@
┊22┊22┊ });
┊23┊23┊ },
┊24┊24┊ addMessage(type: MessageType, chatId: string, content: string) {
+┊ ┊25┊ if (!this.userId) throw new Meteor.Error('unauthorized',
+┊ ┊26┊ 'User must be logged-in to create a new chat');
+┊ ┊27┊
┊25┊28┊ check(type, Match.OneOf(String, [ MessageType.TEXT ]));
┊26┊29┊ check(chatId, nonEmptyString);
┊27┊30┊ check(content, nonEmptyString);@@ -36,6 +39,7 @@
┊36┊39┊ return {
┊37┊40┊ messageId: Messages.collection.insert({
┊38┊41┊ chatId: chatId,
+┊ ┊42┊ senderId: this.userId,
┊39┊43┊ content: content,
┊40┊44┊ createdAt: new Date(),
┊41┊45┊ type: typeThis requires us to update the Message model as well so TypeScript will recognize the changes:
@@ -19,6 +19,7 @@
┊19┊19┊export interface Message {
┊20┊20┊ _id?: string;
┊21┊21┊ chatId?: string;
+┊ ┊22┊ senderId?: string;
┊22┊23┊ content?: string;
┊23┊24┊ createdAt?: Date;
┊24┊25┊ type?: MessageTypeNow we can determine if a message is ours or not in the MessagePage thanks to the senderId field we've just added:
@@ -18,6 +18,7 @@
┊18┊18┊ message: string = '';
┊19┊19┊ autoScroller: MutationObserver;
┊20┊20┊ scrollOffset = 0;
+┊ ┊21┊ senderId: string;
┊21┊22┊
┊22┊23┊ constructor(
┊23┊24┊ navParams: NavParams,@@ -26,6 +27,7 @@
┊26┊27┊ this.selectedChat = <Chat>navParams.get('chat');
┊27┊28┊ this.title = this.selectedChat.title;
┊28┊29┊ this.picture = this.selectedChat.picture;
+┊ ┊30┊ this.senderId = Meteor.userId();
┊29┊31┊ }
┊30┊32┊
┊31┊33┊ private get messagesPageContent(): Element {@@ -55,8 +57,6 @@
┊55┊57┊ }
┊56┊58┊
┊57┊59┊ findMessagesDayGroups() {
-┊58┊ ┊ let isEven = false;
-┊59┊ ┊
┊60┊60┊ return Messages.find({
┊61┊61┊ chatId: this.selectedChat._id
┊62┊62┊ }, {@@ -67,8 +67,7 @@
┊67┊67┊
┊68┊68┊ // Compose missing data that we would like to show in the view
┊69┊69┊ messages.forEach((message) => {
-┊70┊ ┊ message.ownership = isEven ? 'mine' : 'other';
-┊71┊ ┊ isEven = !isEven;
+┊ ┊70┊ message.ownership = this.senderId == message.senderId ? 'mine' : 'other';
┊72┊71┊
┊73┊72┊ return message;
┊74┊73┊ });Now we're going to add the abilities to log-out and edit our profile as well, which are going to be presented to us using a popover. Let's show a popover any time we press on the options icon in the top right corner of the chats view.
A popover, just like a page in our app, consists of a component, view, and style:
@@ -0,0 +1,75 @@
+┊ ┊ 1┊import { Component, Injectable } from '@angular/core';
+┊ ┊ 2┊import { Alert, AlertController, NavController, ViewController } from 'ionic-angular';
+┊ ┊ 3┊import { PhoneService } from '../../services/phone';
+┊ ┊ 4┊import { LoginPage } from '../login/login';
+┊ ┊ 5┊import { ProfilePage } from '../profile/profile';
+┊ ┊ 6┊
+┊ ┊ 7┊@Component({
+┊ ┊ 8┊ selector: 'chats-options',
+┊ ┊ 9┊ templateUrl: 'chats-options.html'
+┊ ┊10┊})
+┊ ┊11┊@Injectable()
+┊ ┊12┊export class ChatsOptionsComponent {
+┊ ┊13┊ constructor(
+┊ ┊14┊ private alertCtrl: AlertController,
+┊ ┊15┊ private navCtrl: NavController,
+┊ ┊16┊ private phoneService: PhoneService,
+┊ ┊17┊ private viewCtrl: ViewController
+┊ ┊18┊ ) {}
+┊ ┊19┊
+┊ ┊20┊ editProfile(): void {
+┊ ┊21┊ this.viewCtrl.dismiss().then(() => {
+┊ ┊22┊ this.navCtrl.push(ProfilePage);
+┊ ┊23┊ });
+┊ ┊24┊ }
+┊ ┊25┊
+┊ ┊26┊ logout(): void {
+┊ ┊27┊ const alert = this.alertCtrl.create({
+┊ ┊28┊ title: 'Logout',
+┊ ┊29┊ message: 'Are you sure you would like to proceed?',
+┊ ┊30┊ buttons: [
+┊ ┊31┊ {
+┊ ┊32┊ text: 'Cancel',
+┊ ┊33┊ role: 'cancel'
+┊ ┊34┊ },
+┊ ┊35┊ {
+┊ ┊36┊ text: 'Yes',
+┊ ┊37┊ handler: () => {
+┊ ┊38┊ this.handleLogout(alert);
+┊ ┊39┊ return false;
+┊ ┊40┊ }
+┊ ┊41┊ }
+┊ ┊42┊ ]
+┊ ┊43┊ });
+┊ ┊44┊
+┊ ┊45┊ this.viewCtrl.dismiss().then(() => {
+┊ ┊46┊ alert.present();
+┊ ┊47┊ });
+┊ ┊48┊ }
+┊ ┊49┊
+┊ ┊50┊ handleLogout(alert: Alert): void {
+┊ ┊51┊ alert.dismiss().then(() => {
+┊ ┊52┊ return this.phoneService.logout();
+┊ ┊53┊ })
+┊ ┊54┊ .then(() => {
+┊ ┊55┊ this.navCtrl.setRoot(LoginPage, {}, {
+┊ ┊56┊ animate: true
+┊ ┊57┊ });
+┊ ┊58┊ })
+┊ ┊59┊ .catch((e) => {
+┊ ┊60┊ this.handleError(e);
+┊ ┊61┊ });
+┊ ┊62┊ }
+┊ ┊63┊
+┊ ┊64┊ handleError(e: Error): void {
+┊ ┊65┊ console.error(e);
+┊ ┊66┊
+┊ ┊67┊ const alert = this.alertCtrl.create({
+┊ ┊68┊ title: 'Oops!',
+┊ ┊69┊ message: e.message,
+┊ ┊70┊ buttons: ['OK']
+┊ ┊71┊ });
+┊ ┊72┊
+┊ ┊73┊ alert.present();
+┊ ┊74┊ }
+┊ ┊75┊}@@ -0,0 +1,13 @@
+┊ ┊ 1┊<ion-content class="chats-options-page-content">
+┊ ┊ 2┊ <ion-list class="options">
+┊ ┊ 3┊ <button ion-item class="option option-profile" (click)="editProfile()">
+┊ ┊ 4┊ <ion-icon name="contact" class="option-icon"></ion-icon>
+┊ ┊ 5┊ <div class="option-name">Profile</div>
+┊ ┊ 6┊ </button>
+┊ ┊ 7┊
+┊ ┊ 8┊ <button ion-item class="option option-logout" (click)="logout()">
+┊ ┊ 9┊ <ion-icon name="log-out" class="option-icon"></ion-icon>
+┊ ┊10┊ <div class="option-name">Logout</div>
+┊ ┊11┊ </button>
+┊ ┊12┊ </ion-list>
+┊ ┊13┊</ion-content>@@ -0,0 +1,13 @@
+┊ ┊ 1┊.chats-options-page-content {
+┊ ┊ 2┊ .options {
+┊ ┊ 3┊ margin: 0;
+┊ ┊ 4┊ }
+┊ ┊ 5┊
+┊ ┊ 6┊ .option-name {
+┊ ┊ 7┊ float: left;
+┊ ┊ 8┊ }
+┊ ┊ 9┊
+┊ ┊10┊ .option-icon {
+┊ ┊11┊ float: right;
+┊ ┊12┊ }
+┊ ┊13┊}It requires us to import it in the NgModule as well:
@@ -5,6 +5,7 @@
┊ 5┊ 5┊import { StatusBar } from '@ionic-native/status-bar';
┊ 6┊ 6┊import { MomentModule } from 'angular2-moment';
┊ 7┊ 7┊import { ChatsPage } from '../pages/chats/chats';
+┊ ┊ 8┊import { ChatsOptionsComponent } from '../pages/chats/chats-options';
┊ 8┊ 9┊import { LoginPage } from '../pages/login/login';
┊ 9┊10┊import { MessagesPage } from '../pages/messages/messages';
┊10┊11┊import { ProfilePage } from '../pages/profile/profile';@@ -19,7 +20,8 @@
┊19┊20┊ MessagesPage,
┊20┊21┊ LoginPage,
┊21┊22┊ VerificationPage,
-┊22┊ ┊ ProfilePage
+┊ ┊23┊ ProfilePage,
+┊ ┊24┊ ChatsOptionsComponent
┊23┊25┊ ],
┊24┊26┊ imports: [
┊25┊27┊ BrowserModule,@@ -33,7 +35,8 @@
┊33┊35┊ MessagesPage,
┊34┊36┊ LoginPage,
┊35┊37┊ VerificationPage,
-┊36┊ ┊ ProfilePage
+┊ ┊38┊ ProfilePage,
+┊ ┊39┊ ChatsOptionsComponent
┊37┊40┊ ],
┊38┊41┊ providers: [
┊39┊42┊ StatusBar,Now we will implement the method in the ChatsPage which will initialize the ChatsOptionsComponent using a popover controller:
@@ -1,9 +1,10 @@
┊ 1┊ 1┊import { Component, OnInit } from '@angular/core';
┊ 2┊ 2┊import { Chats, Messages } from 'api/collections';
┊ 3┊ 3┊import { Chat } from 'api/models';
-┊ 4┊ ┊import { NavController } from 'ionic-angular';
+┊ ┊ 4┊import { NavController, PopoverController } from 'ionic-angular';
┊ 5┊ 5┊import { Observable } from 'rxjs';
┊ 6┊ 6┊import { MessagesPage } from '../messages/messages';
+┊ ┊ 7┊import { ChatsOptionsComponent } from './chats-options';
┊ 7┊ 8┊
┊ 8┊ 9┊@Component({
┊ 9┊10┊ templateUrl: 'chats.html'@@ -11,7 +12,9 @@
┊11┊12┊export class ChatsPage implements OnInit {
┊12┊13┊ chats;
┊13┊14┊
-┊14┊ ┊ constructor(private navCtrl: NavController) {
+┊ ┊15┊ constructor(
+┊ ┊16┊ private navCtrl: NavController,
+┊ ┊17┊ private popoverCtrl: PopoverController) {
┊15┊18┊ }
┊16┊19┊
┊17┊20┊ ngOnInit() {@@ -40,4 +43,12 @@
┊40┊43┊ Chats.remove({_id: chat._id}).subscribe(() => {
┊41┊44┊ });
┊42┊45┊ }
+┊ ┊46┊
+┊ ┊47┊ showOptions(): void {
+┊ ┊48┊ const popover = this.popoverCtrl.create(ChatsOptionsComponent, {}, {
+┊ ┊49┊ cssClass: 'options-popover chats-options-popover'
+┊ ┊50┊ });
+┊ ┊51┊
+┊ ┊52┊ popover.present();
+┊ ┊53┊ }
┊43┊54┊}The method is invoked thanks to the following binding in the chats view:
@@ -7,7 +7,7 @@
┊ 7┊ 7┊ <button ion-button icon-only class="add-chat-button">
┊ 8┊ 8┊ <ion-icon name="person-add"></ion-icon>
┊ 9┊ 9┊ </button>
-┊10┊ ┊ <button ion-button icon-only class="options-button">
+┊ ┊10┊ <button ion-button icon-only class="options-button" (click)="showOptions()">
┊11┊11┊ <ion-icon name="more"></ion-icon>
┊12┊12┊ </button>
┊13┊13┊ </ion-buttons>As for now, once you click on the options icon in the chats view, the popover should appear in the middle of the screen. To fix it, we gonna add the extend our app's main stylesheet, since it can be potentially used as a component not just in the ChatsPage, but also in other pages as well:
@@ -14,3 +14,16 @@
┊14┊14┊// To declare rules for a specific mode, create a child rule
┊15┊15┊// for the .md, .ios, or .wp mode classes. The mode class is
┊16┊16┊// automatically applied to the <body> element in the app.
+┊ ┊17┊
+┊ ┊18┊// Options Popover Component
+┊ ┊19┊// --------------------------------------------------
+┊ ┊20┊
+┊ ┊21┊$options-popover-width: 200px;
+┊ ┊22┊$options-popover-margin: 5px;
+┊ ┊23┊
+┊ ┊24┊.options-popover .popover-content {
+┊ ┊25┊ width: $options-popover-width;
+┊ ┊26┊ transform-origin: right top 0px !important;
+┊ ┊27┊ left: calc(100% - #{$options-popover-width} - #{$options-popover-margin}) !important;
+┊ ┊28┊ top: $options-popover-margin !important;
+┊ ┊29┊}| < Previous Step | Next Step > |
|---|