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
Is your feature request related to a problem? Please describe.
Right now, wasm calls to other components use the same codegen config as the base operations. This can cause issues if inner calls need raw access while the parent operation is simple enough to use the generated decoding logic.
Propose a solution
Along with component.op_name() calls, expose a component.op_name_raw() (or similiar) that exposes the raw stream to the caller so they can do what they want.
Describe alternatives you've considered
Better, more flexible codegen configuration but - even still - a raw passthrough would always be useful.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Right now, wasm calls to other components use the same codegen config as the base operations. This can cause issues if inner calls need raw access while the parent operation is simple enough to use the generated decoding logic.
Propose a solution
Along with
component.op_name()
calls, expose acomponent.op_name_raw()
(or similiar) that exposes the raw stream to the caller so they can do what they want.Describe alternatives you've considered
Better, more flexible codegen configuration but - even still - a raw passthrough would always be useful.
The text was updated successfully, but these errors were encountered: