-
Couldn't load subscription status.
- Fork 9
feat: add eval reasons to WASM Bucketing #1091
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
| @@ -355,13 +345,16 @@ describe('SegmentationManager Unit Test', () => { | |||
| platformVersion: '2.0.0', | |||
| platform: 'iOS', | |||
| } | |||
| assert.strictEqual(false, evaluateOperator({ data, operator })) | |||
| assert.deepStrictEqual( | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
all of the assertions in this file have the argument backwards, not sure i should fix in this PR since the changes here are crazy enough
39d817d to
bd37a49
Compare
|
recreating with av |
Add "Eval Reasons" to Variables and Features to report what condition trigger a variation to be served, similar to changes for js library in #1085.