-
Notifications
You must be signed in to change notification settings - Fork 411
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
feat: Introduce the SDK Evaluation Context schema #4414
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 3 Skipped Deployments
|
Docker builds report
|
Uffizzi Ephemeral Environment
|
@khvn26 I love the idea of a schema. |
@novakzaballa One thing I could do to demonstrate is to go ahead and add it for JS and Golang SDK transient ids/traits PRs. You'll be able to review the schema with those implementations in consideration. |
Let's do that @khvn26 . Some examples I generated look good to me and we can always optimize if we see an opportunity while we move forward. I'll approve the PR. Nice job! |
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.
LGTM
793dd11
to
741e68f
Compare
Thanks for submitting a PR! Please check the boxes below:
Contributes to #4413.
docs/
if required so people know about the feature!Changes
The following is a proposed Flagsmith Evaluation Context schema JSON Schema definition.
Notes
IdentityEvaluationContext.traits
is a mapping of trait keys to aTraitEvaluationContext | null
union. In case anull
is provided, we assume intent to delete the previously persisted trait.TraitEvaluationContext.value
can only be astring
now.TraitEvaluationContext.type
enum field designating the trait value type. For now it will support an SDK-side mapping layer. It's expected that the v2 SDK API should support it in the future.How did you test this code?
This is a documentation change, but I'm verifying the schema against a validator.