You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 12, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 12, 2025. It is now read-only.
Feature Flag evaluation not working as expected #52
When I alternate between both key with manager and empty string it seems my feature flag key is always true. I'm assuming this is because my default when active is true is using variant 1 of true. But it says under Variant 1 option the following
This flag is currently active. It will respect individual user targeting and evaluate all rules. If none of these match, it will fall back to the value you configure here.
My understanding is that because of rule number 2 I set on the user where Key is not equal to the string I'm expecting then it will return variant 2 or false. Again this isn't working so not sure if I misunderstood how this should work, or I am doing something wrong.
Happy to create a reproduction if that helps but should be easy to replicate I think.
visitorKey: this is an automatically created key per visitor of your page. it's generated per device and might chance if cookies are lost
user: this identifies a specific user that exists in your application. you can provide a user and would typically supply your user's id as the user key. a user always needs to have at least a key. happykit supports a specific set of known attributes for users.
traits: this is any key-value pair you want to provide
You might be running into trouble as happykit doesn't expect an empty user key
Could you try using a trait instead? That would be recommended here
Could you try using a non-empty user key? Just for debugging purposes
So I have tried with traits and same issue it always resolves to true.
const { initialFlagState } = await getFlags({
context,
traits: [{
// key: 'manager', // this should be true
key: 'test', // this should be false
}],
})
console.log('initialFlagState', initialFlagState)
Activity
dferber90 commentedon May 18, 2023
Hey, thanks for the super detailed report!
HappyKit currently accepts three forms of inputs:
You might be running into trouble as happykit doesn't expect an empty user key
hect1c commentedon May 18, 2023
Hey thanks for the reply.
So I have tried with traits and same issue it always resolves to
true.screenshot of the rules

screenshot of the

initialFlagStateoutputdferber90 commentedon May 18, 2023
Looks like the error is here:
traitsexpects an object, but you are providing an array. Could you try with this?