Skip to content

Conversation

@phaym
Copy link
Contributor

@phaym phaym commented Jun 11, 2025

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.

  • updated tests to include the expected eval reason

@vercel
Copy link

vercel bot commented Jun 11, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
js-sdks-web-elements ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 18, 2025 2:12pm
js-sdks-with-provider ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 18, 2025 2:12pm
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
js-sdks-next-js-page-router ⬜️ Ignored (Inspect) Jun 18, 2025 2:12pm

@phaym phaym changed the title Feat/assembly eval reasons 2 feat: wasm eval reasons Jun 16, 2025
@phaym phaym changed the title feat: wasm eval reasons feat: add eval reasons for WASM Bucketing Jun 16, 2025
@@ -355,13 +345,16 @@ describe('SegmentationManager Unit Test', () => {
platformVersion: '2.0.0',
platform: 'iOS',
}
assert.strictEqual(false, evaluateOperator({ data, operator }))
assert.deepStrictEqual(
Copy link
Contributor Author

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

@phaym
Copy link
Contributor Author

phaym commented Jun 18, 2025

recreating with av

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants