You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Entity values in Bionic can be accessed in two ways: from another entity definition, or directly from a flow with Flow.get. Currently these two APIs offer different ways to transform and aggregate the values.
When accessing entity values from the definition of another entity, there's a powerful @gather decorator that joins many values of many entities into a single dataframe. When using Flow.get, one can only aggregate the values of a single entity. However, get provides other options for accessing serialized values, which aren't available from within entity definitions.
These discrepancies make certain constructions impossible, and they also make the system harder to learn. In particular, new users often find it difficult to understand the @gather decorator -- I believe this is partly because there's no way to access gathered values directly from a flow, which makes it hard to experiment.
We should move towards a unified API where the same functionality is available in both circumstances. Perhaps something like these:
Entity values in Bionic can be accessed in two ways: from another entity definition, or directly from a flow with
Flow.get
. Currently these two APIs offer different ways to transform and aggregate the values.When accessing entity values from the definition of another entity, there's a powerful
@gather
decorator that joins many values of many entities into a single dataframe. When usingFlow.get
, one can only aggregate the values of a single entity. However,get
provides other options for accessing serialized values, which aren't available from within entity definitions.These discrepancies make certain constructions impossible, and they also make the system harder to learn. In particular, new users often find it difficult to understand the
@gather
decorator -- I believe this is partly because there's no way to access gathered values directly from a flow, which makes it hard to experiment.We should move towards a unified API where the same functionality is available in both circumstances. Perhaps something like these:
The text was updated successfully, but these errors were encountered: