Hare/yoi
1
1
Fork 0
Code Actions Packages Releases Activity

fix: declare plugin service websocket authority

Browse Source
This commit is contained in:
Hare
2026-06-25 16:52:20 +09:00
parent 7a4fd97526
commit 6c8998878d
5 changed files with 44 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
resources/plugin/templates/rust-component-instance/README.md
+1 -1
View File
@@ -5,6 +5,6 @@ This template targets the Component Model-only runtime (`runtime.kind = "wasm-co
It demonstrates both authoring surfaces supported by a shared Plugin instance:
- `example_echo` is an ordinary request/response Tool handler.
- `example_ws` is a Service ingress handler. The host owns WebSocket receive/reconnect work and dispatches bounded `websocket_text` events into `handle_ingress`. The guest replies by returning a `websocket_send` output command in `ServiceOutput`; do not run a guest-side `recv(timeout)` polling loop.
- `example_ws` is a Service ingress handler. The host owns WebSocket receive/reconnect work and dispatches bounded `websocket_text` events into `handle_ingress`. The guest replies by returning a `websocket_send` output command in `ServiceOutput`; do not run a guest-side `recv(timeout)` polling loop. The manifest declares `host_api.websocket` plus a matching `[[websocket]]` target for the example URL. Enablement grants must explicitly allow the same WebSocket target before the host will send output commands.
Build with `cargo component build --release` (or the project-specific build command used by your Plugin packaging flow), then run `yoi plugin check` / `yoi plugin pack` from the generated Plugin directory.