ChannelBuilderUI

This project was generated with Angular CLI version 1.0.4.

Run ChannelBuilderUI

1. Install dependencies
    i. Open the ".npmrc" file and remove all content in the file except for "package-lock=false"
        (This is required only for npm install. You can undo this after npm install completes. This should not be checked in.)
    ii. Open a Command Prompt or Terminal to the ChannelBuilderUI project
    iii. Execute the following command: npm install. Wait for the dependencies to install

2. Log In to V5:
    You'll need to log in to V5 to successfully authenticate ChannelBuilderUI.

    i. Login to the client facing V5 QA login page of whichever client you want to use on local or through admintool.
        Ex: https://acehardware.v5qa.brandmuscle.net/Login/Login.aspx?ReturnUrl=%2f or https://admintool.v5qa.brandmuscle.net/Login/Login.aspx?ReturnUrl=%2f
    ii. Login with your credentials(admintool) or use appropriate users configured for that client for qa. 
    iii. If using your own credentials through admintool, ensure to assign appropriate user group for CFM access to your userId.
    iv. In ChannelBuilderUI → app.config.ts, ensure to update the above url to which you logged in to at
            if (environment.envName === 'local') {
                this.config._v5OpenIdUrl = 'https://acehardware.v5qa.brandmuscle.net/api/v5oidc/v1';
                this.config._redirectUrl = 'https://localhost:4200';
            }
        .Ex: If using admintool, replace only acehardware with admintool. so the new url is https://admintool.v5qa.brandmuscle.net/api/v5oidc/v1.  

3. Run ChannelBuilderUI      
    i. Open a Command Prompt or Terminal to the ChannelBuilderUI project
    ii. Execute the following command: npm start
    iii. On the browser you logged in to the V5 site, go to https://localhost:4200/

Code scaffolding

Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|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. Before running the tests make sure you are serving the app via ng serve.

Further help

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