README.md in guard-rspec-4.2.10 vs README.md in guard-rspec-4.3.0

- old
+ new

@@ -56,11 +56,11 @@ Please read [Guard doc](https://github.com/guard/guard#readme) for more information about the Guardfile DSL. ## Options -Guard::RSpec 4.0 use now a more simple approach with the new `cmd` option that let you precisely define which rspec command will be launched on each run. As example if you want to support Spring with a custom formatter (progress by default) use: +Guard::RSpec 4.0 now uses a simpler approach with the new `cmd` option that let you precisely define which rspec command will be launched on each run. This option is required due to the number of different ways possible to invoke rspec, the template now includes a default that should work for most applications but may not be optimal for all. As example if you want to support Spring with a custom formatter (progress by default) use: ``` ruby guard :rspec, cmd: 'spring rspec -f doc' do # ... end @@ -81,12 +81,12 @@ ``` ruby cmd: 'zeus rspec' # Specify a custom rspec command to run, default: 'rspec' spec_paths: ['spec'] # Specify a custom array of paths that contain spec files failed_mode: :focus # What to do with failed specs # Available values: - # :focus (default) - focus on the first 10 failed specs, rerun till they pass + # :focus - focus on the first 10 failed specs, rerun till they pass # :keep - keep failed specs until they pass (add them to new ones) - # :none - just report + # :none (default) - just report all_after_pass: true # Run all specs after changed specs pass, default: false all_on_start: true # Run all the specs at startup, default: false launchy: nil # Pass a path to an rspec results file, e.g. ./tmp/spec_results.html notification: false # Display notification after the specs are done running, default: true run_all: { cmd: 'custom rspec command', message: 'custom message' } # Custom options to use when running all specs