Assignment Details Part 1 of 7: AssignmentDetails return object and supporting classes #175
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
aarsilv
changed the title
aarsilv
commented
Dec 10, 2025
| * | ||
| * @param <T> The type of the variation value (Boolean, Integer, Double, String, etc.) | ||
| */ | ||
| public class AssignmentDetails<T> { |
Contributor
Author
There was a problem hiding this comment.
This is the top-level class that will be returned by get<type>Details() methods.
We use generics so that the customer's code doesn't have to unwrap an EppoValue if they retrieve the variation (which is top level, typed T).
This was referenced Dec 10, 2025
typotter
reviewed
Dec 18, 2025
| public class AllocationDetails { | ||
| private final String key; | ||
| private final AllocationEvaluationCode allocationEvaluationCode; | ||
| private final int orderPosition; |
Collaborator
There was a problem hiding this comment.
You're making Twitch happy with this!
typotter
approved these changes
Dec 18, 2025
| import java.util.List; | ||
|
|
||
| /** | ||
| * Contains comprehensive debugging information about a flag evaluation. This includes why a |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
📚Assignment Details Stacked Pull Requests📚
👉 AssignmentDetails return object and supporting classes (#175)
🔲 Parse more UFC metadata (#176)
🔲 Ingest details part of shared test cases (#177)
🔲 FlagEvaluator computes details (#183)
🔲 Ability to unwrap EppoValue to a given type (#184)
🔲 Public assignment details methods (#181)
🔲 Bandit details (#182)
Eppo Internal
🎟️ Ticket: FFESUPPORT-378 - Implement assignment details for common Java core
Motivation and Context
We want to bring detailed assignment capabilities (e.g.,
get<Type>Details()) to Android and Java SDKs.Description
This pull request gets the ball rolling by preparing the return type that the
get<Type>Details()methods will return.This is a generic
AssignmentDetails<T>, whereTwill beBoolean,Integer,Double,String, orJsonNode. The template type allows the top levelvariationof the details to be the desired type without the customer having to unbox.How has this been documented?
Documentation will be updated for the upstream SDKs once this is incorporated into them
How has this been tested?
This chunk is untested in this pull request as they are currently unused, but will be tested later on by changes to
FlagEvaluatorTest,BaseEppoClientTest, andBaseEppoClientBanditTest.