Repository navigation
plugins: use plugin ids for management actions - #3284
Conversation
|
/claude review |
Claude reviewNo issues found. Verified the ID switch is correct end to end: Checked: signature/caller consistency, ID-vs-name keying in QML and Go, model fields, no new strings or catalog edits. Model: claude-opus-5. |
(cherry picked from commit 433b13c)
Description
Plugin registry entries expose a stable ID and a human-readable name. The UI was passing the display name to management operations and then using it to index ID-keyed plugin state, which fails when the name and ID differ.
This change uses the ID for install, update, uninstall, enablement, registry lookup, desktop defaults, and widget instance creation, while retaining the display name for user-facing notifications. The existing DMS RPC method and payload shape remain unchanged.
Type of change
Related issues
N/A
Screenshots / video
N/A — no visual change.
Checklist
I18n.tr()with translator context, reusing existing terms where possible (not applicable: no new strings)make fmt, added/updated tests,make testpasses, andgo mod tidyis clean (not applicable: no Go changes)make lint-qmlwith no new warningsLocal verification
uvx prek run --files ...: all configured hooks passed for the five changed filesqmldom --dump-ast: all five changed QML files parse successfullygit diff --check: passedmake lint-qmlcould not be completed locally because the packaged Quickshell 0.3.1 installation does not provide the QML module type metadata required byqmllint; CI is left to perform the repository-native lint check