search

cloudflavor / skyforge

The WASI plugins, the spec and the registry used by skyforge plugins.
Apache License 2.0
0 stars 0 forks source link

Move to WIT #1

Closed PI-Victor closed 4 months ago

PI-Victor commented 4 months ago

Context

Right now the interface between the WASM plugins and the client is defined as a json spec, which is read at runtime and each time the client loads a plugin and then compares the functions exported by the wasm plugin to the json defined spec.

Description

Instead of using a json spec for defining the interface between the client and the WASM plugins, the spec should be defined in WIT.

Acceptance Criteria

The plugins have a minimal interface defined. The client is able to use this interface to interact with the plugin implementation

PI-Victor commented 4 months ago

/triage /assign

PI-Victor commented 4 months ago

goes together with https://github.com/cloudflavor/skycrane/issues/21

linear[bot] commented 4 months ago

CLO-56 Move to WIT

PI-Victor commented 4 months ago

/label R&D Feature

PI-Victor commented 4 months ago

done in https://github.com/cloudflavor/skyforge/pull/2 /close