mantacode / feature-toggle-lib Goto Github PK

If you, for instance, define traffic as

"foo": {
  "exclusiveSplit": true,
  "traffic": 1,
  "features": {
    "a": {
      "traffic": 0.33
    },
    "b": {
      "traffic": 0.33
    },
    "c": {
      "traffic": 0.33
    }
  }
}

We've observed that this typically throws "Cannot read property 'isFeatureEnabled' of undefined" somewhere in our routes/middleware. This might not be only with exclusiveSplits . . . it might be when the inner traffic does not add up to the parent traffic.

We're running into the problem - now that we're working in 3 teams with traffic split evenly - that one team needs to bump the ftoggle version for a test they're deploying, but that can have negative affects on tests another team already has running (because people who are cookied into a treatment get reassigned). If we could either version features directly or else exclude features from version checking altogether, that would be handy.