Travis-CI integration, please.

Most packages are safe from vulnerabilities, if out-of-date. GitHub have alerted us to a known security vulnerability:

Pls. update dependencies and correct vulnerabilities.

needs some 2020 coding practices applied.

in addition to equals, above, below, please add a validation method for "between", such that

          "criteria": [
            {
              "has": {
                "trait": "hasNumberValue",
                "comparison": "between",
                "start": 1,
                "end": 10
              }
            }
          ]
        },

This would cut improve on the compound criteria that includes an "above" and a "below" with an "all" match.

There are several instances of debug using multiple : to try and prefix debug logs (for instance brie:criteria:has) further than one level. Unfortunately this does not work, resulting in no logs at all.

https://github.com/visionmedia/debug#conventions

While it would be nice to be able to filter using multiple levels of prefixes, debug doesn't support this usage. We should remove all instances of multi-level prefixing, and replace it with a strategy of using underscores instead: brie:criteria_has.

Run npm install --save-dev [email protected] to resolve 1 vulnerability

SEMVER WARNING: Recommended action is a potentially breaking change

We list nested key support for is, but has does not properly support traits pointing to nested keys. For instance:

let data = {
    ua: {
        os: {
            name: 'Mac OS',
            version: '10.11.6'
        }
    }
};
let flagsIn = {
    "isMac": {
        "criteria" : [ 
            {
                "has": {
                    "trait": "ua.os.name",
                    "comparison": "equals",
                    "value": "Mac OS"
                }
            }
        ]
    }
};

The current identification of traits does not allow for nested keys, and fails:
brie:criteria Evaluation data has trait (ua.os.name)? false +0ms

We should add support for nested trait keys, which would allow for more flexibility in data and criteria.

npm audit security report

Run npm install --save-dev [email protected] to resolve 2 vulnerabilities

SEMVER WARNING: Recommended action is a potentially breaking change

Run npm install [email protected] to resolve 1 vulnerability

Run npm install [email protected] to resolve 1 vulnerability

SEMVER WARNING: Recommended action is a potentially breaking change

Run npm update lodash --depth 4 to resolve 3 vulnerabilities

Run npm update debug --depth 3 to resolve 1 vulnerability

Fix the build. Travis is failing at NVM install command because node version 8.6.13 is not available. Upgrade to non-specific
lts/*

Given a data object like

{
  id: 1234567,
  importantDateValue: '12-12-2022'
}

and given a criteria value like

"isNewerThanImportantDate": {
  "criteria": [
    {
      "has": {
        "trait": "importantDateValue",
        "comparison": "younger",
        "value": "12-01-2022"
      }
    }
  ]
}

Expected result should be true since the human-readable dates are different and since the data object date of December 12 is newer than the comparison date of December 1.

Note:

new Date('12-12-2022') ==> Mon Dec 12 2022 00:00:00 GMT-0800 (Pacific Standard Time)
new Date('12-Dec-2022') ==> Mon Dec 12 2022 00:00:00 GMT-0800 (Pacific Standard Time)
new Date('12/12/2022') ==> Mon Dec 12 2022 00:00:00 GMT-0800 (Pacific Standard Time)
new Date('12.12.22') ==> Mon Dec 12 2022 00:00:00 GMT-0800 (Pacific Standard Time)

Date comparison strings could be try'd before comparison. Since younger and older are limited to Date access, some pre-validation could be implemented.