fix: custom context properties are respected during evaluation #333
Conversation
This file contains 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
sighphyre
changed the title
sighphyre
changed the title
for more information, see https://pre-commit.ci
sjaanus
approved these changes
Nov 22, 2024
sighphyre
deleted the
fix/custom-context-properties-are-moved-to-properties
branch
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.
This forces custom context properties in the
propertiesfield on the context before sending it to Yggdrasil. Previously the Python SDK would treat all context properties the same, which is a pretty big deviation from other SDKs. This re-enables this behavior in a way that Yggdrasil can handle