From b2d4c3c2eaabf1cfd385192c004fd12e44d3ad17 Mon Sep 17 00:00:00 2001 From: John Bintz Date: Tue, 24 May 2011 06:22:01 -0400 Subject: [PATCH] readme tweak --- README.md | 18 +++++++++++++++--- 1 file changed, 15 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index ada1ed3..1e904ef 100644 --- a/README.md +++ b/README.md @@ -1,10 +1,22 @@ -Whoa, it works with Guard! So fast! +## Guard support for jasmine-headless-webkit + +Add running your Jasmine specs to your `Guardfile` via [`jasmine-headless-webkit`](http://github.com/johnbintz/jasmine-headless-webkit/). Nice! guard 'jasmine-headless-webkit' do watch(%r{^app/assets/javascripts/(.*)\..*}) { |m| newest_js_file("spec/javascripts/#{m[1]}") } end -Guard options: +## `guard` options -* `:all_on_start => false` to not run everything +* `:all_on_start => false` to not run everything, just like `guard-rspec` + +## What's the deal with `newest_js_file`? + +Since one could, theoretically, have a CoffeeScript app file and a JavaScript spec file (or vice versa), the search for the correct matching +file is a little more complicated. `newest_js_file` extends the Guard DSL to search the given path for the newest `.js` or `.coffee` file: + + newest_js_file('spec/javascripts/models/my_model') + #=> search for Dir['spec/javascripts/models/my_model*.{js,coffee}'] and return the newest file found + +If you 100% know you won't need that support, modify your `Guardfile` as appropriate.