Skip to content

Skip registering [email protected] interfaces in DevPluginManager #11

@brooksmtownsend

Description

@brooksmtownsend

Description

The DevPluginManager::register_plugin method currently skips only the wasmcloud:wash/plugin export when registering plugin component instances. However, it should also skip registering [email protected] interfaces to avoid conflicts and unnecessary registrations.

Location

crates/wash/src/dev.rs:58 in the register_plugin method

Current Behavior

The code currently only filters out wasmcloud:wash/plugin interfaces:

match name.split_once('@') {
    Some(("wasmcloud:wash/plugin", _)) => {
        trace!(name, "skipping internal plugin export");
        continue;
    }
    // ... rest of logic
}

Proposed Solution

Add logic to also skip [email protected] interfaces, likely by checking if the interface name starts with wasi: and has version 0.2.

Context

This is part of the development loop's plugin system where plugins export WebAssembly component instances that need to be registered with the runtime. Standard WASI interfaces shouldn't need to be registered as they're typically provided by the runtime itself.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions