Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable/Disable All button for options #3535

Closed
pastelmind opened this issue Sep 7, 2020 · 2 comments · Fixed by #6949
Closed

Enable/Disable All button for options #3535

pastelmind opened this issue Sep 7, 2020 · 2 comments · Fixed by #6949
Labels
meta Related to Refined GitHub itself

Comments

@pastelmind
Copy link

pastelmind commented Sep 7, 2020

Currently we have a large list of options. I'd like to enable only some of them and disable the rest, but going through all of them is very tedious. An "Enable/disable all" toggle button would be great.

Alternative ideas that would probably take more development resources:

  • A filterable, sortable dynamic config list
  • A search bar in the config page that supports filters like is:disabled or is:enabled
@fregante
Copy link
Member

fregante commented Sep 7, 2020

As said before:

Refined GitHub adds features that benefit everyone or almost everyone, so we don’t expect people to look around and pick what they want.

You should only deactivate features if you find something you disagree with. None of us wants to spend hours on the options UI to slightly improve it.

@fregante fregante closed this as completed Sep 7, 2020
@fregante fregante added meta Related to Refined GitHub itself and removed enhancement under discussion labels Sep 7, 2020
@fregante
Copy link
Member

fregante commented Sep 8, 2020

  • A search bar in the config page that supports filters like is:disabled or is:enabled

Disabled features float to the top automatically, just refresh the page

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Related to Refined GitHub itself
Development

Successfully merging a pull request may close this issue.

2 participants