I'm not sure I agree with his behavior change.  I could imagine a scenario where a user has the following switches:

* `new` - turned on only for beta testers.
* `new:feature_1` - global, consenting
* `new:featuer_2` - 50% of users, consenting

Given the current logic, if `active('new:feature_1')` was called, it would first check its parent `new` switch, and iff it's enabled, would it then check its own status and return `True` or `False` (it's `True` in this case since it's global).  This functionality works nicely since you can have a "gating" parent switch that only funnels in a select group of requests (here admins) and then all the child switches can consent with it first, applying their logic to any requests that make it though.

With this new logic, if `new:feature_1` is global, `active('new:feature_1')` returns `True` *immediately*, even if `new:feature_1` is consenting and `new` doesn't apply.  IMO that's not the way it should work, but happy to hear arguments against it.