We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When the scope is changed to a group with a different set of plugins, plugin instances aren't stopped and started automatically.
E.g. guard-livereload is not started (Guard::LiveReload#start not called) if it isn't in the default group on startup.
Guard::LiveReload#start
I believe switching groups should restart every plugin, since different instances can have different configs.
So this is a major change inside Guard, since this was never properly implemented.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When the scope is changed to a group with a different set of plugins, plugin instances aren't stopped and started automatically.
E.g. guard-livereload is not started (
Guard::LiveReload#start
not called) if it isn't in the default group on startup.I believe switching groups should restart every plugin, since different instances can have different configs.
So this is a major change inside Guard, since this was never properly implemented.
The text was updated successfully, but these errors were encountered: