Add precomputed assignment fixtures#12
Draft
leoromanovsky wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Flutter and other precompute-based clients need shared fixtures that validate the
/precompute-assignmentsresponse shape and the SDK side effects that happen after local typed evaluation. The existing fixtures cover UFC evaluator behavior, but not the client-side precomputed assignment contract used by mobile and browser SDKs.Changes
This adds a new
precomputed/fixture area with documentation and two initial cases. The cases cover successful typed assignments for boolean, string, integer, float, and object values, plus exposure/flagevaluation emission counts. They also coverdoLog: false, unknown variation isolation, type mismatch defaults, and missing-flag defaults.Decisions
The precomputed fixtures are separate from
evaluation-cases/because they validate a different contract: client SDKs consume an already-evaluated assignment payload instead of evaluating UFC locally. Each case includes context, precompute response, typed evaluations, and expected emission counts so downstream SDKs can run deterministic tests without Datadog credentials.