修雨 a056a9abfb refactor(plugin): purge removed plugin settings instead of merely disabling ...

Review follow-up on #126: RemovePlugin used to call
setPluginEnabled(name, false), which left the plugin's key in
EnabledPlugins and never touched PluginConfigs. settings.json retained
dangling state for plugins no longer on disk.

Replace the disable with purgePluginFromSettings, which deletes both
the EnabledPlugins entry and any PluginConfigs entry for the removed
plugin, leaving unrelated plugins' state intact. A re-install defaults
to enabled=true via the existing install paths, matching user
expectations.

Covered by TestRemovePluginPurgesSettings across both user and legacy
managed layouts.

2026-04-19 14:32:22 +08:00

..

converter.go

feat(plugin): inject user identity (UserID, CorpID) into stdio plugin subprocesses

2026-04-17 10:02:26 +08:00

hook_adapter.go

feat(plugin): add plugin system core framework

2026-04-16 09:33:20 +08:00

loader_config_test.go

feat(plugin): add persistent plugin config via settings.json

2026-04-16 09:38:18 +08:00

loader.go

refactor(plugin): purge removed plugin settings instead of merely disabling

2026-04-19 14:32:22 +08:00

manifest.go

fix(plugin): harden plugin system security boundaries

2026-04-16 10:53:53 +08:00

plugin_test.go

refactor(plugin): purge removed plugin settings instead of merely disabling

2026-04-19 14:32:22 +08:00