This is part one of the intrinsics work, adding support to SDF while filtering these out on the front end so there's no impact to users.
Intrinsic Functions will rely on the existing Attribute Bindings subsystem (as opposed to adding another abstraction as with Leaf Funcs). For now, we are filtering out component specific bindings, and bindings for Input Sockets as these will not be configurable by users.
Now, when listing functions, we include Attribute Bindings for the Identity and Unset Functions, so that we can expose the ability for users to configure identity funcs in the UI as opposed to using the asset builder setValueFrom() or having to create an attribute function that simply returns another prop/socket.
This enables us to build the experience for configuring them, but we can ship this without having that completed as there is no noticeable impact to users (just returning more data that we're not showing)
This is part one of the intrinsics work, adding support to SDF while filtering these out on the front end so there's no impact to users.
Intrinsic Functions will rely on the existing Attribute Bindings subsystem (as opposed to adding another abstraction as with Leaf Funcs). For now, we are filtering out component specific bindings, and bindings for Input Sockets as these will not be configurable by users.
Now, when listing functions, we include Attribute Bindings for the Identity and Unset Functions, so that we can expose the ability for users to configure identity funcs in the UI as opposed to using the asset builder
setValueFrom()or having to create an attribute function that simply returns another prop/socket.This enables us to build the experience for configuring them, but we can ship this without having that completed as there is no noticeable impact to users (just returning more data that we're not showing)
via The Roku Channel on GIPHY