Allow hiding individual plugins or keywords from plugin indicator

Open
  • Is something wrong?
#4,743 0 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
desktop, search

Research direction

Start by reading the plugin indicator implementation and its settings code to find how plugins and their keywords are added to the home screen and indicator results. Compare the two proposed options in the issue and check existing context menu and settings patterns in the repository. Done means users can hide individual plugins or keywords and those choices are respected in the relevant results.

Written by the indexing model from the issue text.

Description

enhancement keep-fresh kind/ux

See this reddit post for an example of the problem: https://www.reddit.com/r/FlowLauncher/comments/1xoe410/how_to_control_home_screen_ordering/

It should not be an all or nothing decision, a user should be able to choose exactly which plugins (or ideally plugin keywords) he wants to be visible in the home screen or the plugin indicators own results (via its keyword)

I can think of two methods to implement this, ideally we should have both:

  1. A context menu option on the result that lets you hide it
  2. A menu in the settings page of the plugin indicator that lets you toggle each plugin keyword it would show
Dominant language
C#
Stars
16k
Forks
673
Avg merge
2d 5h
Merged PRs (30d)
9

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Flow-Launcher/Flow.Launcher

All issues in Flow-Launcher/Flow.Launcher

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.