-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Flag evaluation not working as expected #52
Comments
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
|
Hey thanks for the reply. So I have tried with traits and same issue it always resolves to
|
Looks like the error is here:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey,
I'm testing out Happykit Feature flags and ran into an issue or possibly I have a misunderstanding of how the feature flag evaluation works.
I have the following rules setup.
In my
getServerSideProps
I have the following codeWhen 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
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.
The text was updated successfully, but these errors were encountered: