ntbang0901
835a9c883c
Plugins could not rely on each other: nothing said "this plugin needs that one", and a plugin had no way to let others extend it. Plugin API 1.5 adds both. - `[[depends]]` in `plugin.toml` (version range, `optional`). A plugin whose required dependency is missing, disabled, the wrong version, cyclic or unable to run is shown as Blocked with the reason and starts once the dependency can run again. Plugins start in dependency order; disabling a plugin others need asks first. Granting or revoking a dependency's permissions also settles its dependents. - `[[extension-points]]` declares points with typed fields. Dependents contribute to them from `plugin.toml` (checked at install time); the owner reads them through the read-only `extensions` interface (`host::extension_contributions`) and hears changes through the `extensions-changed` event. The plugin details page shows what a plugin requires, who requires it, and its extension points with their contributors. Covered by the `ext-owner` fixture and `plugin_dependencies.rs`. Co-authored-by: ntbang0901 <121003585+ntbang0901@users.noreply.github.com>
container-runner — API 1.4 example
Put this directory on PATH before installing/granting the plugin, so
process:openidea-example-wrapper resolves to the included executable. Run
Example: Register Container Wrapper in a trusted project. It registers a
project run target, opens a keyed terminal, writes an Output channel and sets
a window status item. The owned terminal-exited event updates that window.
Disable withdraws the target; terminal/output lifetimes follow the host rules.
The fake wrapper just executes argv locally and exits its demo terminal.
To adapt it to DDEV, declare process:ddev, change program to ddev,
args to ["exec"], and use command overrides such as
("composer", ["composer"]). For Lando declare process:lando and supply its
CLI's command prefixes. Only approved executables run; selecting one in
Settings › Plugins reapproves/pins it. No shell command strings are evaluated.
For mapped working directories set container_root and workdir_args using
your wrapper's documented argv convention (for example --cwd {cwd}), or let
the wrapper manage cwd. Environment forwarding also belongs to that wrapper.
Build from the repository root:
plugins/build.sh official/container-runner
cargo test --manifest-path plugins/official/container-runner/Cargo.toml
cargo run -p ide-host --bin openidea-plugin -- check plugins/official/container-runner
Install the built package folder through Settings › Plugins › Install from Disk. See the plugin guide and official/community policy.
On Windows, supply an equivalent approved executable; the included demo script requires a POSIX shell. The host API itself is cross-platform.