angular-feature-flags

This repo is forked from https://github.com/michaeltaranto/angular-feature-flags which is no longer being supported. This version provides support for functionality specifically needed by PageUp, your milage may vary.

An AngularJS module that allows you to control when you release new features in your app by putting them behind feature flags/switches. This module only supports Angular v1.2 and up.

The idea

Abstracting your application functionality into small chunks and implementing them as loosely coupled directives. This allows you to completely remove sections of your application by simply toggling a single dom element.

How it works

The basic premise is you write your feature and wrap it up in a directive, then where you implement that directive in your markup you add the feature-flag directive to the same element. You can then pass the key of the flag to this directive to resolve whether of not this feature should be enabled.

The module pulls a json file down which defines the feature flags and which ones are active. If enabled angular will process the directive as normal, if disabled angular will remove the element from the dom and not compile or execute any other directives is has.

You can then add the override panel to your app and turn individual features on override the server values, saving the override in local storage which is useful in development.

Flag data

The flag data that drives the feature flag service is a json format. Below is an example:

[
    { "key": "...", "active": "...", "name": "...", "description": "..." },
    ...
]

Setting flag data

Flag data can be set via the featureFlags service using the set method. This currently accepts either a HttpPromise or a regular Promise. The promise must resolve to a valid collection of flag data.

For example, if you were loading your flag data from a remote JSON file:

var myApp = angular.module('app', ['feature-flags']);

myApp.run(function(featureFlags, $http) {
  featureFlags.set($http.get('/data/flags.json'));
});

Setting flag data on config phase (≥ v1.1.0)

From version v1.1.0 you can also initialize the feature flags in the config phase of your application:

var myApp = angular.module('app', ['feature-flags']);

myApp.config(function(featureFlagsProvider) {
  featureFlagsProvider.setInitialFlags([
    { "key": "...", "active": "...", "name": "...", "description": "..." },
  ]);
});

Toggling elements

The feature-flag directive allows simple toggling of elements based on feature flags, e.g:

<div feature-flag="myFlag">
  I will be visible if 'myFlag' is enabled
</div>

If you need to hide elements when a flag is enabled, add the feature-flag-hide attribute, e.g:

<div feature-flag="myFlag" feature-flag-hide>
  I will *NOT* be visible if 'myFlag' is enabled
</div>

Running the demo

Running the demo is easy assuming you have Gulp installed:

• Checkout the project
• Switch to the directory
• Run 'gulp demo'

Should launch the demo in your default browser

Running the unit test

This relies on Gulp also obviously, to run the test suite:

• Checkout the project
• Switch to the directory
• Run 'gulp test'

Deploying a new version

• Create feature branch, do your work and make a pull request
• Get the pull request approved, squash and merge onto master

$ git checkout master
$ npm version patch
$ git push
$ git push --tags

You can also use npm version major or npm version minor depending on whether you've made breaking changes

License

MIT