Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Expose raw wasm-to-component call #368

Closed
jsoverson opened this issue Jul 13, 2023 · 1 comment
Closed

Expose raw wasm-to-component call #368

jsoverson opened this issue Jul 13, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@jsoverson
Copy link
Contributor

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.

@jsoverson jsoverson added the enhancement New feature or request label Jul 13, 2023
@jsoverson
Copy link
Contributor Author

Added via #371

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant