class Guard::Plugin
plugins.
the ‘Guard::GuardName` instance will be removed from the active Guard
If one of those methods raises an exception other than `:task_has_failed`,
from a watcher, you can set the `any_return` option to true.
paths to Guard, but if your Guard plugin wants to allow any return value
Watchers for a Guard plugin should return a file path or an array of files
at `lib/guard/guard-name/templates/Guardfile`.
Each Guard plugin should provide a template Guardfile located within the Gem
end
end
throw :task_has_failed
if !runner.run()
def run_all
@example Throw :task_has_failed
@see Guard::Group
@see Guard::Hooker
@see Guard::Base
tasks will be aborted when the group has set the `:halt_on_fail` option.
your Guard plugin method was not successful, and successive Guard plugin
for further evaluation. You can throw `:task_has_failed` to indicate that
method is not evaluated by Guard, but it’ll be passed to the “_end” hook
you want to support this kind of task. The return value of each Guard task
In each of these Guard task methods you have to implement some work when
implemented separately with a specific behavior.
(additions, modifications, removals) in once, or each task can be
{#run_on_changes} could be implemented to handle all the changes task case
modification.
{#run_on_removals}) task methods depending on user interaction and file
{#run_on_changes} ({#run_on_additions}, {#run_on_modifications} and
Guard will trigger the {#start}, {#stop}, {#reload}, {#run_all} and
Base class from which every Guard plugin implementation must inherit.
def initialize(options = {})
(**options)- 
        any_return(Boolean) -- allow any object to be returned from
- 
        group(Symbol) -- the group this Guard plugin belongs to
- 
        watchers(Array) -- the Guard plugin file
Parameters:
- 
        options(Hash) -- the Guard plugin options
def initialize(options = {}) _set_instance_variables_from_options(options) _register_callbacks end