geofmureithi / plugy Goto Github PK

Currently we dont have any way of differentiating between plugins that are rightly done eg have all methods defined and a junk wasm file.
This causes a panic at calltime and rightly so.

Is there a way to add some signature or check to prevent loading a wasm file that doesn't conform.

Add optional wasi support.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• fix(deps): update rust crate anyhow to v1.0.86
• fix(deps): update rust crate darling to v0.20.9
• fix(deps): update rust crate proc-macro2 to v1.0.84
• fix(deps): update rust crate serde to v1.0.203
• fix(deps): update rust crate syn to v2.0.66
• fix(deps): update rust crate wasmtime to v18.0.4
• fix(deps): update rust crate wasmtime to v21
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Currently this works:

#[plugy::plugin]
trait Greeter {
    fn greet(&self) -> String;
}

This may not:

#[plugy::plugin]
trait Greeter {
    fn greet(&self, name:String) -> String;
}

Is generics a worthy cause?
Currently they can work on guest but the warpper code generated doesn't

there are dog.wasm, cat.wasm and much more plugins, these are provided by community, and keep growing. the host app is fixed, so it's impossible to define struct for each plugin in host app code, like current example in repo.

the host app needs to use plugin based on user input. i tried a bit but fail.

Imagine doing this:

let context = Context::new(); // Context shared by plugins
let runtime = Runtime::new(context);

Then on guest:

#[plugy::plugin]
trait Greeter {
    fn greet(&self, ctx:Context) -> String;
}

Context can expose methods like fetch etc which would have external access for guests.