Ingage Directory

This project was generated with Angular CLI version 8.3.21.

Installation

1. This Project requires a global installation of angular, using the command "npm install -g @angular/cli"

2. Use the link from "clone with https" option on the project github page to enter the git command "git clone [html link here]". Then run "git pull".

3. To Ensure you are in the development branch, run command "git checkout development"

4. Access the google drive folder(_Ingage Share/F: Project SPaces/IngageDirectory/data-files) and download the 3 environment files, and add them to ingage-directory/src/environments within the project directory.

5. Within the project directory, run the command "npm install"

Launching Project Locally

The project should launch by running the command "ng serve" in a new terminal, but if you receive compile errors, run the commands "ng update" and "npm update" before trying again.

Feature Creation

When creating a new feature, to avoid merge conflicts, please run the command "git checkout -b [feature-name-here]" to create a branch for your feature.

Data/Environments

This project uses a static json file for it's data source. There are three environment configurations

default configuration

The default configuation uses the employee.mock.json file for employee data. This is fictional data, and the related images are stored in the 'assets/test-profiles` folder for local testing. All of the files needed to run the default configuation are part of this repo.

test configuration

The test configuation uses the employee.test.json file for employee data. This is a subset of the production data, isn't normally updated. The employee.test.json file is not part of this repo, see Tony Maddox for a copy.

production configuration

The production configuation uses the employee.prod.json file for employee data. This file is generated regularly from a Google Sheet that is maintained by Tony Maddox. The employee.prod.json file is not part of this repo.

Development server

Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Firebase

This app is hosted on Firebase. Use npm run deploy to build & deploy to Firebase. See Tony Maddox for access to the firebase project.

Code scaffolding

Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.

Build

Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the --prod flag for a production build.

Running unit tests

Run ng test to execute the unit tests via Karma.

Running end-to-end tests

Run ng e2e to execute the end-to-end tests via Protractor.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI README.

setup prod/stagging in firebase

https://dev.to/valentinprgnd/multiple-environments-with-firebase-hosting-1ao4

https://scotch.io/tutorials/deploying-an-angular-cli-app-to-production-with-firebase

feature requests

• search on mobile (from Andrea)
• employee service (read from static json file)
• employee service (read from "live" data source, TBD)
• add a count of consultants at each client to left menu
• add coach to profile (from Andrea)
• look at https://www.npmjs.com/package/@angular/fire for implementing anayltics
• use firebase authentication
• tighten up authentication, are there better practices?
• if viewing yourself, show your Munoz coupon code
• document configuration, how to build locally, how to push to firebase, etc.
• show "champion a cause" per Elena on detail page. we may even want a list of people and cause???