Angular gulp

Project for creating a generic gulp file for angularJS applications.

Installation

$ npm install

To get started run:

$ gulp {{command}}

Git

To ensure code does not get lost or altered through bad merging the following practice will be used by all developers. The basis for the strategy is Workflow, as can be found here.

Branches

Branches will be made on a per-feature basis. Feature branches will be should be named clearly and be relevant to the feature being developed. This branch can then be used by multiple developers if needed. Features will be structured such that no other work is dependent on this feature being deployed. Other branches will be releases and hotfixes. These will be used in accordance with the git Workflow model.

New Components

A Gulp command is available to add new components to the application based on agreed format and structure. Components available are:

• Controller
• Directive (simple and complex)
• Factory
• Filter
• Modal
• Route (new URL destination for application)
• Service

To execute

gulp add
#Provides dialog to choose component

gulp add:<component>
#Replace <component> with desired component

Tests

The Gulp file comes with some prebuilt test commands. Unit tests are executed by Karma and QA/E2E tests are done by Protractor.

Style

Three tools are/will be used to check code, JSCS, JSHint and HTML Lint (specific to Angular). These have specific gulp tasks calls:

#jscs
gulp test:jscs

#jshint
gulp test:jshint


Both can be run with a simple command of:
```sh
gulp test:lint

Also, it is possible to target each of the lint tests at a directory (-d) or file (-f)

gulp test:lint -f fileToBeTested.js

gulp test:lint -d folder/to/be/tested/

Unit

Unit tests are written in Jasmine and are executed by Karma. Coverage of tests is provided by Istanbul.

gulp test:unit