Repository navigation
Decouple Wrap, Plugin, & App Bindings From CLI #1696
Description
Is your feature request related to a problem? Please describe.
Currently, the wrap wasm & plugin bindings are bundled into the CLI. This means that every time bindings have an update, we have to create a new release of the CLI.
Describe the solution you'd like
Ideally we could import bindings into the CLI through an external link of some sort. Since the schema-bind package is a JS package, we could use NPM package references, and import the binding module from there. Alternatively a github URL could be used.
Ultimately we'd like to have bindings be built as wraps, so it could be a wrap URI in the future.
Activity
[-]Decouple Wrap & Plugin Bindings From CLI[/-][+]Decouple Wrap, Plugin, & App Bindings From CLI[/+]dOrgJelli commentedon Apr 24, 2023
app/andplugin/project bindings can live in the client repos. For example:rust-client=>app/rust&plugin/rustpython-client=>app/python&plugin/pythonjavascript-client=>app/typescript&plugin/typescriptThe
wasm/project bindings can live in a new "wrap" repo. For example:rust-wrap=>wasm/rustassemblyscript-wrap=>wasm/assemblyscriptNOTE: we should consider changing
wasm/towrap/.NOTE: we should consider changing
app/typescripttoapp/javascript, or alternativelyjavascript-clienttotypescript-client.dOrgJelli commentedon May 10, 2023
Quick update: I started working on wrap port of the bindings here https://github.com/polywrap/wrap-abi-bindgen/tree/dev
I had some extra time today and thought this would be fun to get started on. Once implemented this will make the implementation of the above much simpler, as invoking wraps dynamically within the CLI is much easier than NPM packages.