Unify AnyValues
across all SDKs and use archetype_field_name
as discriminator
#10074
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.
Related
AnyValues
should use argument names to setarchetype_field_name
metadata #9906.AnyValues
wrapper to Rust and C++ APIs #9340.What
This PR does multiple things:
AnyValues
interface that is similar across Python 🐍 , C++ 🌊 , and Rust 🦀 SDKs (so far we only haveAnyValues
in Python).kwargs
(i.e. the name of the field toarchetype_field_name
instead ofcomponent_name
.AnyValues
we ensure that more of the logged data is actually tagged.TODOs