Support for configuring multiple dimension values in a single settings block

See #44

The following:

[
    {
        settings: ['region:US'],
        value: 'foo'
    },
    {
        settings: ['region:CA'],
        value: 'foo'
    }
]

can now be combined into a single block:

[
    {
        settings: ['region:CA,US'],
        value: 'foo'
    }
]

Support for multiple dimension values

See [#43]

This adds the ability for context values to be an array where merge precedence is in index order. While using multiple values will impact performance (less than adding a new dimension) this implementation ensures that using string values will continue to have the same performance characteristics.

More Read Optimizations

• [#41] Precalculation of dimension order
• [#42] Optimization of settings merge

Bug fix for empty dimensions

Fixed a bug when YCB was used without dimensions.

1.3.0: Optimizations

• Ability to disable substitutions via ycb.read(dimensions, { applySubstitutions: false });
• Internal optimizations for read calls

release 1.2.2

A small release that just added an example to the README, and set the license in package.json so that it'd appear on the npm website.

bugfix

• PR #34: settings with invalid dimension should be ignore and warning should be issued

release 1.2.0

This is a small release with one bug fix.

• [fixed #26] Settings under unknown dimension value no longer overwrite master settings
• now built and tested on node 0.10 and 0.11, linted with jshint (instead of jslint)

release 1.1.1

This is a repackaging of the previous release ("0.1.1") with the correct version number.

release 0.1.1

This release contains one fix:

• #28 #29 Fix for ycb not replacing empty values

Thanks to @pranavparikh for the pull request!