microsoft/PowerToys

PowerToys Run should provide a mechanism to disable plugins if they're missing dependencies

Open

#18,406 opened on May 20, 2022

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C# (7,978 forks)batch import
Help WantedIdea-EnhancementProduct-PowerToys RunRun-Plugin

Repository metrics

Stars
 (133,154 stars)
PR merge metrics
 (Avg merge 14d 20h) (117 merged PRs in 30d)

Description

Description of the new feature / enhancement

The VS Code plugin can be toggled on even if you don't have VS Code installed. IMO, it should be disabled and grayed out in the settings page, with a message indicating why.

This could be accomplished by a new interface in Wox.Plugin which plugins could implement to report back a status saying whether they can be enabled or not, and if not a string saying why.

Scenario when this would be used?

For the VS Code plugin, and other plugins that depend on the presence of various dependencies. For example, a OneNote plugin would require OneNote installed, the Everything plugin depends on Everything, a Graph plugin would require an MSA logged in, etc.

Supporting information

No response

Contributor guide

Research direction
Explore the Wox.Plugin interface and how plugins register. Determine where to add a new interface method for reporting dependency status.
Tech stack
csharp
Domain
desktopdeveloper experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#Plugin architecture knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60