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

Disable auto restart after plugin install by default #3028

Open
jjw24 opened this issue Oct 15, 2024 · 2 comments
Open

Disable auto restart after plugin install by default #3028

jjw24 opened this issue Oct 15, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@jjw24
Copy link
Member

jjw24 commented Oct 15, 2024

For new user experience, Flow shouldn't restart automatically after plugin installs, otherwise have to keep navigate back to the Plugin Store to continue installing more plugins.

Let's change the default behaviour and disable auto restart after plugin installation.

@jjw24 jjw24 added the bug Something isn't working label Oct 15, 2024
@jjw24 jjw24 changed the title Change the default behaviour of auto restart after plugin install Disable auto restart after plugin install by default Oct 15, 2024
@Fludem
Copy link

Fludem commented Oct 20, 2024

I agree. In fact, I'd go as far as saying the setting should be removed entirely.

Instead, the MessageBox should prompt the user to choose whether to restart now or later.

There's no need to bury a setting within the settings of an individual plugin. Also, the choice to restart now or later is always situational.

For instance, enabling this setting could be helpful if it didn't require confirmation to restart and you were only doing a CRUD on one plugin.

If I happen to be installing multiple plugins, disabling it would make the most sense. That would mean going out of my way to toggle it off before installing my new plugins and then back on once I was finished.

At this point, this feature is only causing me problems instead of solving any.

To wrap it back up, my points are:

  • The setting is hidden away and not in a prominent location.

  • Even if it were in a prominent location, would it be causing more problems than clicking a button for now/later?

Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 60 days.\n\nAlternatively this issue can be kept open by adding one of the following labels:\nkeep-fresh

@github-actions github-actions bot added the Stale label Dec 20, 2024
@jjw24 jjw24 removed the Stale label Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants